| 2 |
Approval of Agenda |
|
| R1-2001500 |
Draft Agenda of RAN1#100bis-e meeting |
RAN1 Chair |
| R1-2002748 |
RAN1#100bis-e Meeting_x00B_Timelines, Scope, Process |
RAN1 Chair, MCC |
| R1-2002749 |
Additional Guidelines for RAN1#100b e-Meeting Management |
RAN1 Chair |
| 3 |
Highlights from RAN plenary |
|
| R1-2001501 |
Highlights from RAN#87-e relevant to RAN1 |
RAN1 Chair |
| 4 |
Approval of Minutes from previous meeting |
|
| R1-2001502 |
Report of RAN1#100-e meeting |
ETSI MCC |
| R1-2002747 |
Report of RAN1#100-e meeting |
ETSI MCC |
| 5 |
Incoming Liaison Statements |
|
| R1-2001503 |
LS on power control for NR-DC |
RAN2, vivo |
| R1-2001504 |
LS to RAN4 on measurement range and granularity |
RAN2, Intel |
| R1-2001505 |
LS on eMIMO RRC parameters |
RAN2, Ericsson |
| R1-2001506 |
LS on random access procedure in NR-U |
RAN2, InterDigital |
| R1-2001507 |
LS on DCP |
RAN2, Huawei |
| R1-2001508 |
LS to RAN1 on preamble-to-PRU mapping for 2-step CFRA |
RAN2, Ericsson |
| R1-2001509 |
LS on the applicability of UE capability for NE-DC |
RAN2, ZTE |
| R1-2001510 |
LS to RAN1 on T-delta in IAB |
RAN2, Samsung |
| R1-2001511 |
LS to RAN1 on the starting point of MSGB window |
RAN2, ZTE |
| R1-2001512 |
Reply LS on signaling of Q for a serving cell in NR-U |
RAN2, Qualcomm |
| R1-2001513 |
Guidelines for UE capability definitions |
RAN2, Ericsson, Intel |
| R1-2001514 |
LS on dormant BWP configuration and related operation |
RAN2, OPPO |
| R1-2001515 |
Reply LS on updates for TS 36.300 and TS 38.300 |
RAN3, Ericsson |
| R1-2001516 |
Reply LS on UAV positioning |
SA1, InterDigital |
| R1-2001517 |
LS on open PUR issues for NB-IoT/eMTC |
RAN2, Ericsson |
| R1-2001518 |
LS on NR coexistence |
RAN2, Qualcomm |
| R1-2001519 |
Reply LS on CSI-RS capabilities (FG 2-33/36/40/41/43) |
RAN2, NTT DOCOMO |
| R1-2001520 |
LS on gNB measurements report mapping for NR Positioning |
RAN4, Ericsson |
| R1-2001521 |
LS on UL LBT failure recovery for the target cell |
RAN4, Ericsson |
| R1-2001522 |
LS on Tx switching between two uplink carriers |
RAN4, Apple |
| R1-2001523 |
Reply LS on CLI measurement capability |
RAN4, Huawei |
| R1-2001580 |
Draft reply LS on DCP |
ZTE |
| R1-2001581 |
Discussion on secondary DRX group |
ZTE |
| R1-2001582 |
Draft reply LS on secondary DRX group |
ZTE |
| R1-2001590 |
Draft reply LS on UE capabilities of CSI-RS |
ZTE |
| R1-2001591 |
Draft reply LS on eMIMO parameters |
ZTE |
| R1-2001627 |
[DRAFT] Reply LS on Tx switching between two uplink carriers |
ZTE |
| R1-2001628 |
[DRAFT] Reply LS on the applicability of UE capabilities for NE-DC |
ZTE |
| R1-2001629 |
[DRAFT] Reply LS on dormant BWP configuration and related operation |
ZTE |
| R1-2001630 |
Discussion on dormant BWP configuration and related operation |
ZTE |
| R1-2001637 |
Draft reply LS on eMIMO RRC parameters |
vivo |
| R1-2001638 |
Draft Reply LS on dormant BWP configuration and related operation |
vivo |
| R1-2001639 |
Discussion on preamble-to-PRU mapping for 2-step CFRA |
vivo |
| R1-2001640 |
Discussion on the starting point of MSGB window |
vivo |
| R1-2001641 |
Discussion on random access procedure in NR-U |
vivo |
| R1-2001642 |
Discussion on MAC-PHY interactions for DCP and CSI reporting |
vivo |
| R1-2001693 |
Discussion on 2nd DRX group |
vivo |
| R1-2001716 |
[Draft] Reply LS on the starting point of MsgB window |
ZTE, Sanechips |
| R1-2001717 |
[Draft] Reply LS on the support of 2-step CFRA |
ZTE, Sanechips |
| R1-2001718 |
Discussion on the LS for the random access procedure in NR-U |
ZTE, Sanechips |
| R1-2001744 |
Discussion on eMIMO RRC parameters |
OPPO |
| R1-2001771 |
Draft reply LS on dormant BWP configuration and related operation |
OPPO |
| R1-2001838 |
Draft LS reply on dormant BWP configuration and related operation |
MediaTek Inc. |
| R1-2001845 |
Discussion on impact of secondary DRX group |
MediaTek Inc. |
| R1-2001848 |
Discussion on RAN2 LS on NR coexistence |
ZTE |
| R1-2001849 |
Discussion on RAN2 LS on open PUR issues |
ZTE |
| R1-2001901 |
Draft reply LS on CSI-RS capabilities (FG 2-33/36/40/41/43) |
vivo |
| R1-2001909 |
Draft reply LS on eMIMO RRC parameters |
LG Electronics |
| R1-2001931 |
Discussion on signaling of Q for a serving cell in NR-U |
LG Electronics |
| R1-2001946 |
Draft Reply LS on random access procedure in NR-U |
LG Electronics |
| R1-2001947 |
Draft Reply LS on the starting point of MSGB window |
LG Electronics |
| R1-2001948 |
Draft Reply LS on preamble-to-PRU mapping for 2-step CFRA |
LG Electronics |
| R1-2001966 |
LS/o on synchronization of Y.DNI-fr “Framework and Requirements of Decentralized Trustworthy Network Infrastructure” in Q2/13 |
ITU-T SG13, China Telecom, Huawei |
| R1-2001980 |
Draft reply LS on CSI-RS capabilities |
Intel Corporation |
| R1-2002051 |
Discussion on RAN2 LS on dormant BWP configuration and related operation |
Futurewei |
| R1-2002055 |
Discussion on RAN2 LS on dormant BWP configuration and related operation |
LG Electronics |
| R1-2002056 |
Discussion on the RAN1 impacts on Secondary DRX group |
CATT |
| R1-2002057 |
Draft reply LS on dormant BWP configuration and related operation |
CATT |
| R1-2002058 |
Draft reply LS on MIMO RRC parameters |
CATT |
| R1-2002099 |
Draft reply to RAN2 LS on eMIMO RRC parameters |
Samsung |
| R1-2002100 |
Draft reply to RAN2 LS on CSI-RS capabilities (FG 2-33/36/40/41/43) |
Samsung |
| R1-2002101 |
Discussion on T_delta in IAB |
Samsung |
| R1-2002102 |
Draft reply LS on preamble-to-PRU mapping for 2-step CFRA |
Samsung |
| R1-2002103 |
Draft reply LS on the starting point of MSGB window |
Samsung |
| R1-2002187 |
Draft reply LS on T_delta in IAB |
LG Electronics |
| R1-2002285 |
Draft LS reply on eMIMO RRC parameters |
Ericsson |
| R1-2002289 |
Draft Reply LS to RAN2 on multi-TRP |
Nokia, Nokia Shanghai Bell |
| R1-2002298 |
[DRAFT] Reply LS on dormant BWP configuration and related operation |
Nokia, Nokia Shanghai Bell |
| R1-2002308 |
[Draft] Reply LS on UE Tx switching period delay and DL interruption |
Apple |
| R1-2002309 |
Discussion on the starting point of MsgB window |
Apple |
| R1-2002310 |
Discussion on NR-U PRACH root sequence and random access procedure for 2-step RACH |
Apple |
| R1-2002311 |
Discussion on preamble-to-PRU mapping for 2-step CFRA |
Apple |
| R1-2002373 |
[DRAFT] LS Response on NR-U PRACH root sequence for 2-step RA |
Ericsson |
| R1-2002374 |
[DRAFT] LS Response on preamble-to-PRU mapping for 2-step CFRA |
Ericsson |
| R1-2002375 |
[DRAFT] LS Response on the starting point of MSGB window |
Ericsson |
| R1-2002376 |
[DRAFT] LS Response on Support of CSI-RS in 2-step CFRA |
Ericsson |
| R1-2002394 |
Discussion on RAN1 specification impact of DL interruption |
CATT |
| R1-2002427 |
[Draft] Reply LS on CSI-RS capabilities (FG 2-33/36/40/41/43) |
NTT DOCOMO, INC |
| R1-2002492 |
Draft LS response on secondary DRX group |
Ericsson |
| R1-2002493 |
On secondary DRX group |
Ericsson |
| R1-2002501 |
On the LS on open PUR issues for NB-IoT/eMTC |
Ericsson |
| R1-2002502 |
On the LS on NR coexistence for NB-IoT/eMTC |
Ericsson |
| R1-2002514 |
Draft response to Reply LS on CSI-RS capabilities |
Qualcomm Incorporated |
| R1-2002515 |
Draft response to LS on dormant BWP configuration and related operation |
Qualcomm Incorporated |
| R1-2002516 |
Discussion on 1Tx-2Tx switching impact in RAN1 |
Qualcomm Incorporated |
| R1-2002578 |
RAN1 impact analysis due to the introduction of secondary DRX cycle |
Huawei, HiSilicon |
| R1-2002602 |
Draft reply LS on NR coexistence |
Huawei, HiSilicon |
| R1-2002603 |
Draft reply LS on open PUR issues for NB-IoT/eMTC |
Huawei, HiSilicon |
| R1-2002615 |
On UE Tx switching period delay and DL interruption |
Nokia, Nokia Shanghai Bell |
| R1-2002657 |
On resouce reservation in NB-IoT and eMTC |
Futurewei |
| R1-2002658 |
Draft LS reply to RAN2 on the starting point of MSGB window |
Huawei, HiSilicon |
| R1-2002659 |
Draft LS reply to RAN2 on preamble-to-PRU mapping for 2-step CFRA |
Huawei, HiSilicon |
| R1-2002660 |
Draft LS reply to RAN2 on support of 2-step CFRA |
Huawei, HiSilicon |
| R1-2002662 |
Draft reply LS on secondary DRX cycle |
Huawei, HiSilicon |
| R1-2002663 |
Draft reply LS on the configuration of ps-TransmitPeriodicCSI and ps-TransmitPeriodicL1-RSRP |
Huawei, HiSilicon |
| R1-2002664 |
Draft LS response to RAN2 LS on dormancy behavior |
Huawei, HiSilicon |
| R1-2002670 |
Discussion on the feasibility of received interference power measurement in NR |
Huawei, HiSilicon |
| R1-2002671 |
Draft Reply LS on the feasibility of received interference power measurement |
Huawei, HiSilicon |
| R1-2002672 |
[Draft] Reply LS on eMIMO RRC parameters |
Huawei, HiSilicon |
| R1-2002673 |
Discussion on Reply LS on CSI-RS capabilities (FG 2-33/36/40/41/43) |
Huawei, HiSilicon |
| R1-2002677 |
[Draft] Reply LS on UL-SL prioritization |
Huawei |
| R1-2002678 |
draft reply LS on the applicability of UE capability for NE-DC |
Huawei, HiSilicon |
| R1-2002680 |
Discussion on the reply LS for SCell dormancy |
Huawei, HiSilicon |
| R1-2002681 |
[Draft] Reply LS on CSI-RS capabilities (FG 2-33/36/40/41/43) |
Huawei, HiSilicon |
| R1-2002691 |
void |
ETSI |
| R1-2002704 |
RAN1#100b-e preparation phase on incoming LS |
RAN1 Chair |
| R1-2002736 |
Outcome of RAN1#100b-e preparation phase on incoming LS |
RAN1 Chair |
| R1-2002760 |
[DRAFT] Reply LS on the applicability of UE capabilities for NE-DC |
ZTE |
| R1-2002761 |
Discussion Summary of LS on UE capability for NE-DC |
Moderator (ZTE) |
| R1-2002792 |
Reply LS on the applicability of UE capabilities for NE-DC |
RAN1, ZTE |
| R1-2002794 |
Reply LS on the starting point of MsgB window |
RAN1, ZTE |
| R1-2002795 |
Reply LS on the support of 2-step CFRA |
RAN1, ZTE |
| R1-2002798 |
LS reply on eMIMO RRC parameters |
RAN1, Ericsson |
| R1-2002799 |
Draft Reply LS on the feasibility of received interference power measurement |
Huawei, HiSilicon |
| R1-2002813 |
Text proposal to correct the reference point of MsgB window in 38.213 |
Moderator (ZTE) |
| R1-2002814 |
Summary of the discussion on the reply LS for MsgB window |
Moderator (ZTE) |
| R1-2002815 |
Summary of the discussion on the reply LS for the support of 2-step CFRA |
Moderator (ZTE) |
| R1-2002900 |
Reply LS on CSI-RS capabilities (FG 2-33/36/40/41/43) |
RAN1, NTT DOCOMO |
| R1-2002901 |
LS Response on preamble-to-PRU mapping for 2-step CFRA |
RAN1, Ericsson |
| R1-2002910 |
Summary of LS on CSI-RS capabilities (FG 2-33/36/40/41/43) |
Moderator (NTT DOCOMO) |
| R1-2002911 |
Discussion on the reply LS on preamble-to-PRU mapping for 2-step CFRA |
Moderator (Ericsson) |
| R1-2002932 |
Reply LS on the feasibility of received interference power measurement |
RAN1, Huawei |
| R1-2002940 |
LS to RAN1 on Guard Symbols in IAB |
RAN2, Samsung |
| R1-2002941 |
LS on the 3GPP work on the NR sidelink |
5GAA WG4, Volkswagen |
| R1-2002952 |
Email Discussion Summary of reply LS on DCP |
Moderator (Huawei) |
| R1-2002953 |
Reply LS on DCP |
RAN1, Huawei |
| R1-2002961 |
LS response on secondary DRX group |
RAN1, Ericsson |
| R1-2002998 |
LS response to dormant BWP configuration and related operation |
RAN1, OPPO |
| R1-2003075 |
LS response to dormant BWP configuration and related operation |
RAN1, OPPO |
| 5.1 |
RAN1 Aspects for RF requirements for NR frequency range 1 (FR1) |
|
| R1-2001626 |
Remaining Issues on Support of Tx Switching between Two Uplink Carriers |
ZTE |
| R1-2001643 |
Potential RAN1 impact to support TDM switching between the 1Tx and 2Tx UL carriers |
vivo |
| R1-2001743 |
Discussion on Tx Switching between Two Uplink Carriers |
OPPO |
| R1-2001821 |
Remaining Details on UE Tx Switching between Two UL Carriers |
MediaTek Inc. |
| R1-2002059 |
Discussion on UL switching |
CATT |
| R1-2002104 |
DL interruption during switching period between 1Tx and 2Tx for two uplink carriers |
Samsung |
| R1-2002190 |
Remaining issues on uplink Tx switching |
China Telecom |
| R1-2002191 |
Summary of uplink Tx switching |
Moderator (China Telecom) |
| R1-2002222 |
On Tx switching between two uplink carriers |
Nokia, Nokia Shanghai Bell |
| R1-2002413 |
RAN1 aspects of UL Tx switching |
Ericsson |
| R1-2002661 |
Discussion on the remaining problems of supporting Tx switching between two uplink carriers |
Huawei, HiSilicon |
| R1-2002724 |
Summary#2 of uplink Tx switching |
Moderator (China Telecom) |
| R1-2002793 |
Summary#3 of uplink Tx switching |
Moderator (China Telecom) |
| R1-2002960 |
Reply LS on UE Tx switching period delay and DL interruption |
RAN1, Apple |
| R1-2002963 |
[100b-e-LS-TxSwitching-01] Email approval of the reply LS for R1-2001522 |
Moderator (China Telecom) |
| R1-2002964 |
[100b-e-LS-TxSwitching-02] Email discussion/approval of the remaining issues for inter-band UL CA |
Moderator (China Telecom) |
| R1-2002965 |
[100b-e-LS-TxSwitching-03] Email discussion/approval of the remaining issues for SUL, EN-DC and other general issues |
Moderator (China Telecom) |
| R1-2003148 |
Introduction of switched uplink operation |
Nokia, Nokia Shanghai Bell |
| 5.2 |
RAN1 Aspects for RF Requirement Enhancements for FR2 |
|
| R1-2001592 |
Enhancement on FR2 MPE mitigation |
ZTE |
| 6.1 |
Maintenance of E-UTRA Releases 8–15 |
|
| R1-2002163 |
[Draft] Correction on WUS related procedure for NB-IoT |
ZTE |
| R1-2002164 |
[Draft] Correction on WUS related procedure for BL/CE UE |
ZTE |
| R1-2002165 |
[Draft] Inclusion of WUS related procedures in TS 36.201 |
ZTE |
| R1-2002166 |
Discussion on WUS transmission in TDD special subframe |
ZTE |
| R1-2002167 |
Draft CR on WUS transmission in TDD special subframe |
ZTE |
| R1-2002171 |
Clarification on set of values for HARQ delay |
Qualcomm Incorporated |
| R1-2002172 |
Clarification on PUCCH collision for HARQ-ACK bundling |
Qualcomm Incorporated |
| R1-2002598 |
Correction on Msg3 NPUSCH retransmission for NB-IoT EDT |
Huawei, HiSilicon |
| R1-2002599 |
Correction on NRS presence in non-anchor carriers for NB-IoT |
Huawei, HiSilicon |
| R1-2002600 |
Correction on NPDCCH monitoring for NB-IoT |
Huawei, HiSilicon |
| R1-2002719 |
RAN1#100b-e preparation phase on Maintenance of E-UTRA Releases 8-15 |
Ad-Hoc Chair (Ericsson) |
| R1-2002768 |
CR on WUS transmission in TDD special subframe |
ZTE |
| R1-2002769 |
Draft CR on excluding TDD special subframes for MWUS maximum and actual duration |
Qualcomm Incorporated |
| R1-2002773 |
Clarification on set of values for HARQ delay |
Qualcomm Incorporated |
| R1-2002774 |
Clarification on set of values for HARQ delay |
Qualcomm Incorporated |
| R1-2002775 |
Clarification on set of values for HARQ delay |
Qualcomm Incorporated |
| R1-2002776 |
Clarification on set of values for HARQ delay |
Qualcomm Incorporated |
| R1-2002777 |
Clarification on PUCCH collision for HARQ-ACK bundling |
Qualcomm Incorporated |
| R1-2002778 |
Clarification on PUCCH collision for HARQ-ACK bundling |
Qualcomm Incorporated |
| R1-2002834 |
Correction on Msg3 NPUSCH retransmission for NB-IoT EDT |
Huawei, HiSilicon |
| R1-2002835 |
Correction on Msg3 NPUSCH retransmission for NB-IoT EDT |
Huawei, HiSilicon |
| R1-2002836 |
Correction on NRS presence in non-anchor carriers for NB-IoT |
Huawei, HiSilicon |
| R1-2002837 |
Correction on NRS presence in non-anchor carriers for NB-IoT |
Huawei, HiSilicon |
| R1-2002838 |
Correction on NRS presence in non-anchor carriers for NB-IoT |
Huawei, HiSilicon |
| R1-2002918 |
CR on WUS transmission in TDD special subframe |
ZTE |
| R1-2002919 |
CR on WUS transmission in TDD special subframe |
ZTE |
| R1-2002920 |
CR on excluding TDD special subframes for MWUS maximum and actual duration |
Qualcomm Incorporated |
| R1-2002921 |
CR on excluding TDD special subframes for MWUS maximum and actual duration |
Qualcomm Incorporated |
| R1-2002957 |
Correction on NPDCCH monitoring for NB-IoT |
Huawei, HiSilicon |
| R1-2002958 |
Correction on NPDCCH monitoring for NB-IoT |
Huawei, HiSilicon |
| R1-2002959 |
Correction on NPDCCH monitoring for NB-IoT |
Huawei, HiSilicon |
| R1-2003126 |
Maintenance of E-UTRA Releases 8-15 |
Ad-Hoc Chair (Ericsson) |
| 6.2 |
Maintenance of E-UTRA Release 16 |
|
| R1-2003132 |
Session notes for 6.2.1 (Maintenance of Additional MTC Enhancements) and 6.2.2 (Maintenance of Additional Enhancements for NB-IoT) |
Ad-Hoc Chair (Samsung) |
| R1-2003150 |
Corrections for Rel-16 NB-IoT features in 36.211 |
Ericsson |
| R1-2003151 |
Corrections to LTE terrestrial broadcast |
Ericsson |
| R1-2003152 |
Corrections to Rel-16 LTE-MTC features in 36.211 |
Ericsson |
| R1-2003153 |
Corrections to DL MIMO efficiency enhancements for LTE |
Ericsson |
| R1-2003154 |
Miscellaneous corrections for Rel-16 NB-IoT features in 36.212 |
Futurewei |
| R1-2003155 |
Corrections to Additional enhancements for NB-IoT |
Motorola Mobility |
| R1-2003156 |
Corrections to LTE-based 5G terrestrial broadcast |
Motorola Mobility |
| R1-2003157 |
Corrections to Additional MTC Enhancements for LTE |
Motorola Mobility |
| R1-2003158 |
Corrections to DL MIMO efficiency enhancements for LTE |
Motorola Mobility |
| R1-2003159 |
Corrections to LTE terrestrial broadcast |
Ericsson |
| R1-2003160 |
void |
Nokia, Nokia Shanghai Bell |
| R1-2003189 |
Cleaned consolidated RRC parameters list for Rel-16 LTE |
Moderator (Qualcomm) |
| 6.2.1.1 |
UE-group wake-up signal |
|
| R1-2001576 |
Corrections on UE-group wake-up signal |
Huawei, HiSilicon |
| R1-2002705 |
FL Summary of Maintenance for group MWUS |
Moderator (Qualcomm Incorporated) |
| 6.2.1.2 |
Support for transmission in preconfigured UL resources |
|
| R1-2001567 |
Corrections on transmission in preconfigured UL resources |
Huawei, HiSilicon |
| R1-2001850 |
Remaining issues for transmission in preconfigured UL resources for MTC |
ZTE |
| R1-2002173 |
Support for transmission in preconfigured UL resources |
Qualcomm Incorporated |
| R1-2002356 |
LTE-M Pre-configured UL Resources Design Considerations |
Sierra Wireless, S.A. |
| R1-2002357 |
Preconfigured UL resources feature lead summary RAN1 #100bis-e |
Moderator (Sierra Wireless) |
| R1-2002503 |
Corrections for Preconfigured UL resources for LTE-MTC |
Ericsson |
| R1-2002641 |
Remaining issues for preconfigured UL resources |
Nokia, Nokia Shanghai Bell |
| R1-2002740 |
Preconfigured UL resources feature lead summary#2 RAN1 #100bis-e |
Moderator (Sierra Wireless) |
| R1-2002800 |
Outcome summary of [100b-e-LTE-eMTC5-PUR-02] on PUR Power Control |
Moderator (Sierra Wireless) |
| R1-2002801 |
Outcome summary of [100b-e-LTE-eMTC5-PUR-01] on eMTC Alignment to NB-IOT |
Moderator (Sierra Wireless) |
| R1-2002962 |
Text Proposals for email [100b-e-LTE-eMTC5-PUR-01] on eMTC Alignment to NB-IOT |
Moderator (Sierra Wireless) |
| R1-2002971 |
Text Proposals for email [100b-e-LTE-eMTC5-PUR-02] on PUR Power Control |
Moderator (Sierra Wireless) |
| 6.2.1.3 |
Scheduling of multiple DL/UL transport blocks |
|
| R1-2001568 |
Corrections on scheduling of multiple transport blocks |
Huawei, HiSilicon |
| R1-2001852 |
Remaining issues on scheduling enhancement for MTC |
ZTE |
| R1-2001928 |
Remaining issues on multiple transport blocks scheduling in MTC |
LG Electronics |
| R1-2002174 |
Scheduling of multiple DL/UL transport blocks |
Qualcomm Incorporated |
| R1-2002504 |
Corrections for Multi-TB scheduling for LTE-MTC |
Ericsson |
| R1-2002512 |
Feature lead summary for Multi-TB scheduling for LTE-MTC |
Moderator (Ericsson) |
| R1-2002642 |
Remaining issues for scheduling of multiple TBs |
Nokia, Nokia Shanghai Bell |
| R1-2002654 |
HARQ-ACK bundling for Multi-TB scheduling |
Futurewei |
| R1-2002796 |
Feature lead summary#2 for Multi-TB scheduling for LTE-MTC |
Moderator (Ericsson) |
| R1-2003112 |
TP for 36.213 on determination of MCS, RV and HARQ ID for LTE-MTC multi-TB scheduling |
Moderator (Ericsson) |
| R1-2003113 |
TP for 36.213 on RV cycling and interleaving granularity for LTE-MTC multi-TB scheduling |
Moderator (Ericsson) |
| R1-2003114 |
TP for 36.213 on HARQ-ACK bundling size for LTE-MTC multi-TB scheduling |
Moderator (Ericsson) |
| 6.2.1.4 |
Coexistence of LTE-MTC with NR |
|
| R1-2001569 |
Corrections on eMTC co-existence with NR |
Huawei, HiSilicon |
| R1-2001855 |
Remaining issues on LTE-MTC resource reservation |
ZTE |
| R1-2002175 |
Coexistence of LTE-MTC with NR |
Qualcomm Incorporated |
| R1-2002505 |
Corrections for NR coexistence performance improvements for LTE-MTC |
Ericsson |
| R1-2002513 |
Feature lead summary for NR coexistence performance improvements for LTE-MTC |
Moderator (Ericsson) |
| R1-2002643 |
Remaining issues for co-existence of eMTC with NR |
Nokia, Nokia Shanghai Bell |
| R1-2002797 |
Feature lead summary#2 for NR coexistence performance improvements for LTE-MTC |
Moderator (Ericsson) |
| R1-2003115 |
TP for 36.211 on TDD special subframe handling for LTE-MTC resource reservation |
Moderator (Ericsson) |
| R1-2003116 |
TP for 36.211 on UL DMRS handling for LTE-MTC resource reservation |
Moderator (Ericsson) |
| R1-2003117 |
TP for 36.213 on SRS handling for LTE-MTC resource reservation |
Moderator (Ericsson) |
| R1-2003118 |
TP for 36.211 on SPS handling for LTE-MTC resource reservation |
Moderator (Ericsson) |
| R1-2003119 |
TP for 36.213 on SPS handling for LTE-MTC resource reservation |
Moderator (Ericsson) |
| 6.2.1.6 |
MPDCCH performance improvement |
|
| R1-2001574 |
Corrections on MPDCCH performance improvement |
Huawei, HiSilicon |
| R1-2001854 |
Clarification on MPDCCH performance improvement |
ZTE |
| R1-2002699 |
Feature lead summary #1 on MPDCCH performance improvement |
Moderator (Huawei) |
| 6.2.1.7 |
CE mode A and B improvements for non-BL UEs |
|
| R1-2001859 |
Correction on CSI-RS based CSI feedback for non-BL UE |
ZTE |
| R1-2001929 |
Corrections on CE mode A and B improvements for non-BL UEs |
LG Electronics |
| R1-2001930 |
FL summary of CE mode A and B improvements for non-BL UEs |
Moderator (LG Electronics) |
| R1-2002735 |
FL summary#2 of CE mode A and B improvements for non-BL UEs |
Moderator (LG Electronics) |
| R1-2002772 |
FL summary#3 of CE mode A and B improvements for non-BL UEs |
Moderator (LG Electronics) |
| R1-2002969 |
Text proposals endorsed through email discussion [100b-e-LTE-eMTC5-non-BL-UEs-01] |
Moderator (LG Electronics) |
| 6.2.1.8 |
Use of LTE Control Channel Region for DL Transmission |
|
| R1-2001860 |
Clarification on use of LTE control region for PUR related DL transmission |
ZTE |
| R1-2002506 |
Corrections for Use of LTE control channel region for LTE-MTC |
Ericsson |
| R1-2002644 |
Feature lead summary on use of LTE control channel region |
Moderator (Nokia) |
| R1-2002993 |
Feature lead summary for [100b-e-LTE-eMTC5-Use-of-LTE-control-channel-region-01] |
Moderator (Nokia) |
| R1-2002994 |
Text Proposals for [100b-e-LTE-eMTC5-Use-of-LTE-control-channel-region-01] |
Moderator (Nokia) |
| 6.2.2.1 |
UE-group wake-up signal |
|
| R1-2001575 |
Corrections on UE-group wake-up signal |
Huawei, HiSilicon |
| 6.2.2.2 |
Support for transmission in preconfigured UL resources |
|
| R1-2001570 |
Corrections on transmission in preconfigured UL resources |
Huawei, HiSilicon |
| R1-2001851 |
Remaining issues for transmission in preconfigured UL resources for NB-IoT |
ZTE |
| R1-2002176 |
Support for transmission in preconfigured UL resources |
Qualcomm Incorporated |
| R1-2002507 |
Corrections for Preconfigured UL resources for NB-IoT |
Ericsson |
| R1-2002640 |
Feature lead summary #1 on transmission in pre-configured UL resources for NB-IoT |
Moderator (Huawei) |
| R1-2002645 |
Remaining issues for preconfigured UL resources |
Nokia, Nokia Shanghai Bell |
| R1-2002714 |
Feature lead summary #2 on transmission in pre-configured UL resources for NB-IoT |
Moderator (Huawei) |
| R1-2002846 |
Reply LS on open PUR issues for NB-IoT/eMTC |
RAN1, Ericsson |
| R1-2002896 |
Email discussion [100b-e-LTE-NB_IoTenh3-PUR-03] on reply LS on open PUR issues for NB-IoT/eMTC |
Moderator (Ericsson) |
| R1-2002942 |
Feature lead summary #1 on [100b-e-LTE-NB_IoTenh3-PUR-01] |
Moderator (Huawei) |
| R1-2002943 |
Feature lead summary #1 on [100b-e-LTE-NB_IoTenh3-PUR-02] |
Moderator (Huawei) |
| R1-2002944 |
LS on PUR working assumption for NB-IoT and eMTC |
RAN1, Huawei |
| R1-2002945 |
Text Proposal on PUR power control for TS 36.213 |
Moderator (Huawei) |
| 6.2.2.3 |
Scheduling of multiple DL/UL transport blocks |
|
| R1-2001571 |
Corrections on scheduling of multiple DL/UL transport blocks |
Huawei, HiSilicon |
| R1-2001853 |
Remaining issues on scheduling enhancement for NB-IoT |
ZTE |
| R1-2002186 |
Scheduling of multiple DL/UL transport blocks |
Qualcomm Incorporated |
| R1-2002508 |
Corrections for Multi-TB scheduling for NB-IoT |
Ericsson |
| R1-2002646 |
Remaining issues for scheduling of multiple TBs |
Nokia, Nokia Shanghai Bell |
| R1-2002692 |
Feature lead summary #1 on multiple TB scheduling for NB-IoT |
Moderator (ZTE) |
| R1-2002741 |
Feature lead summary #2 on multiple TB scheduling for NB-IoT |
Moderator (ZTE) |
| R1-2002909 |
FL summary on [100b-e-LTE-NB_IoTenh3-Multi-TB-03] |
Moderator (ZTE) |
| R1-2002974 |
Text proposal for email discussion on [100b-e-LTE-NB_IoTenh3-Multi-TB-01] |
Moderator (ZTE) |
| R1-2002975 |
Text proposal for email discussion on [100b-e-LTE-NB_IoTenh3-Multi-TB-02] |
Moderator (ZTE) |
| R1-2002976 |
Text proposal for email discussion on [100b-e-LTE-NB_IoTenh3-Multi-TB-03] |
Moderator (ZTE) |
| 6.2.2.4 |
Coexistence of NB-IoT with NR |
|
| R1-2001572 |
Corrections on coexistence of NB-IoT with NR |
Huawei, HiSilicon |
| R1-2001856 |
Remaining issues on NB-IoT resource reservation |
ZTE |
| R1-2002177 |
Coexistence of NB-IoT with NR |
Qualcomm Incorporated |
| R1-2002509 |
Corrections for NR coexistence performance improvements for NB-IoT |
Ericsson |
| R1-2002647 |
Remaining issues for co-existence of NB-IoT with NR |
Nokia, Nokia Shanghai Bell |
| R1-2002700 |
Feature lead summary #1 on coexistence of NB-IoT with NR |
Moderator (Huawei) |
| R1-2002856 |
Outcomes of email discussion [100b-e-LTE-NB_IoTenh3-Coex-NR-04] |
Moderator (Qualcomm Incorporated) |
| R1-2002897 |
Draft LS response on NR coexistence |
Qualcomm |
| R1-2002899 |
LS response on NR coexistence |
RAN1, Qualcomm |
| R1-2002925 |
Feature lead summary #1 on 100b-e-LTE-NB_IoTenh3-Coex-NR-01 |
Moderator (Huawei) |
| R1-2002926 |
Feature lead summary #1 on 100b-e-LTE-NB_IoTenh3-Coex-NR-02 |
Moderator (Huawei) |
| R1-2002927 |
Feature lead summary #1 on 100b-e-LTE-NB_IoTenh3-Coex-NR-03 |
Moderator (Huawei) |
| R1-2003014 |
Text proposal in 100b-e-LTE-NB_IoTenh3-Coex-NR-01 |
Moderator (Huawei) |
| R1-2003015 |
Text proposal in 100b-e-LTE-NB_IoTenh3-Coex-NR-02 |
Moderator (Huawei) |
| R1-2003016 |
Text proposal in 100b-e-LTE-NB_IoTenh3-Coex-NR-03 |
Moderator (Huawei) |
| 6.2.3 |
Maintenance of DL MIMO efficiency enhancements for LTE |
|
| R1-2003133 |
Session notes for 6.2.3 (Maintenance of DL MIMO efficiency enhancements for LTE) |
Ad-Hoc Chair (Samsung) |
| 6.2.3.1.1 |
Additional SRS symbols |
|
| R1-2001573 |
Corrections on additional SRS symbols |
Huawei, HiSilicon |
| R1-2001593 |
Maintenance of additional SRS symbols |
ZTE |
| R1-2001910 |
Text proposals on additional SRS symbols |
LG Electronics |
| R1-2001945 |
Remaining details of additional SRS symbols |
Nokia, Nokia Shanghai Bell |
| R1-2001981 |
Corrections to additional SRS |
Intel Corporation |
| R1-2002178 |
Additional SRS symbols |
Qualcomm Incorporated |
| R1-2002486 |
Maintenance on additional SRS symbols |
Ericsson |
| R1-2002701 |
Feature lead summary #1 on coexistence LTE DL MIMO efficiency enhancement |
Moderator (Huawei) |
| R1-2002928 |
Feature summary on #1 100b-e-LTE-LTE_DL_MIMO_EE-01 |
Moderator (Huawei) |
| R1-2002929 |
Feature summary on #1 100b-e-LTE-LTE_DL_MIMO_EE-02 |
Moderator (Huawei) |
| R1-2003017 |
Text proposal in 100b-e-LTE-LTE_DL_MIMO_EE-01 |
Moderator (Huawei) |
| R1-2003018 |
Text proposal in 100b-e-LTE-LTE_DL_MIMO_EE-02 |
Moderator (Huawei) |
| 6.2.4 |
Maintenance of LTE-based 5G Terrestrial Broadcast |
|
| R1-2002706 |
Summary of issues for LTE-based 5G terrestrial broadcast |
Moderator (Qualcomm Incorporated) |
| R1-2003127 |
Maintenance of LTE-based 5G Terrestrial Broadcast |
Ad-Hoc Chair (Ericsson) |
| 6.2.4.1 |
New numerology(ies) for PMCH for support of rooftop reception |
|
| R1-2001635 |
Corrections to TS 36.211 for the 0.37kHz subcarrier spacing MBSFN |
ZTE |
| R1-2002179 |
Support of longer numerologies for rooftop reception |
Qualcomm Incorporated |
| R1-2002626 |
UE assumptions of MBSFN-RS for new PMCH numerology for support of rooftop reception |
EBU, BBC, IRT |
| R1-2002854 |
Outcomes of email discussion [100b-e-LTE-TerrBcast-01] |
Moderator (Qualcomm Incorporated) |
| R1-2002855 |
Outcomes of email discussion [100b-e-LTE-TerrBcast-02] |
Moderator (Qualcomm Incorporated) |
| R1-2003065 |
Outcomes of email discussion [100b-e-LTE-TerrBcast-01] |
Moderator (Qualcomm Incorporated) |
| R1-2003066 |
Outcomes of email discussion [100b-e-LTE-TerrBcast-02] |
Moderator (Qualcomm Incorporated) |
| 6.2.4.2 |
Necessity and detailed enhancements to the physical channels and signals in the CAS |
|
| R1-2002180 |
Corrections for CAS reception |
Qualcomm Incorporated |
| 6.2.4.4 |
Other |
|
| R1-2001636 |
Text proposal for new numerology in TS 36.214 |
ZTE |
| R1-2002601 |
Text proposal for new numerology in TS 36.201 |
Huawei, HiSilicon |
| 6.2.5 |
LTE Rel-16 UE Features |
|
| R1-2003070 |
LS on updated Rel-16 RAN1 UE features lists for LTE |
RAN1, AT&T, NTT DOCOMO |
| R1-2003071 |
RAN1 UE features list for Rel-16 LTE after RAN1#100bis-E |
Moderators (AT&T, NTT DOCOMO) |
| R1-2003196 |
Summary on email discussion [100b-e-LTE-UEFeatures-Remaining] |
Moderators (AT&T, NTT DOCOMO, INC.) |
| 6.2.5.1 |
UE features for additional MTC enhancements |
|
| R1-2001857 |
Discussion on UE features for additional MTC enhancements |
ZTE |
| R1-2002181 |
UE features for eMTC |
Qualcomm Incorporated |
| R1-2002428 |
Summary on UE features for additional MTC enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2002510 |
On the RAN1 UE feature list for Rel-16 LTE-MTC |
Ericsson |
| R1-2002604 |
Rel-16 UE features for LTE-MTC |
Huawei, HiSilicon |
| R1-2002857 |
Summary on Email discussion [100b-e-LTE-UEFeatures-eMTC-01] |
Moderator (NTT DOCOMO) |
| R1-2002858 |
Summary on Email discussion [100b-e-LTE-UEFeatures-eMTC-02] |
Moderator (NTT DOCOMO) |
| 6.2.5.2 |
UE features for additional enhancements for NB-IoT |
|
| R1-2001858 |
Discussion on UE features for additional enhancements for NB-IoT |
ZTE |
| R1-2002182 |
UE features for NB-IoT |
Qualcomm Incorporated |
| R1-2002429 |
Summary on UE features for additional enhancements for NB-IoT |
Moderator (NTT DOCOMO, INC.) |
| R1-2002511 |
On the RAN1 UE feature list for Rel-16 NB-IoT |
Ericsson |
| R1-2002605 |
Rel-16 UE features for NB-IoT |
Huawei, HiSilicon |
| R1-2002859 |
Summary on Email discussion [100b-e-LTE-UEFeatures-NBIoT-01] |
Moderator (NTT DOCOMO) |
| 6.2.5.3 |
UE features for DL MIMO efficiency enhancements for LTE |
|
| R1-2001594 |
UE features of DL MIMO efficiency enhancements for LTE |
ZTE |
| R1-2001864 |
Summary on UE features for DL MIMO efficiency enhancements for LTE |
Moderator (AT&T) |
| R1-2002160 |
Discussion on RAN1 UE feature for LTE eMIMO |
LG Electronics |
| R1-2002183 |
UE features for MIMO |
Qualcomm Incorporated |
| R1-2002474 |
On UE features for LTE DL MIMO efficiency enhancements |
Ericsson |
| R1-2002606 |
Rel-16 UE features for LTE MIMO |
Huawei, HiSilicon |
| R1-2003081 |
Summary of Email Approval [100b-e-LTE-UEFeatures-MIMO-01] |
Moderator (AT&T) |
| R1-2003082 |
Summary of Email Approval [100b-e-LTE-UEFeatures-MIMO-02] |
Moderator (AT&T) |
| R1-2003083 |
Summary of Email Approval [100b-e-LTE-UEFeatures-MIMO-03] |
Moderator (AT&T) |
| R1-2003084 |
Summary of Email Approval [100b-e-LTE-UEFeatures-MIMO-04] |
Moderator (AT&T) |
| 6.2.5.4 |
UE features for LTE-based 5G terrestrial broadcast |
|
| R1-2001865 |
Summary on UE features for LTE-based 5G terrestrial broadcast |
Moderator (AT&T) |
| R1-2003085 |
Summary of Email Approval [100b-e-LTE-UEFeatures-TERR_BCAST-01] |
Moderator (AT&T) |
| 6.2.5.5 |
Other |
|
| R1-2001755 |
Disconssion on LTE feature list for 5G_V2X_NRSL |
OPPO |
| R1-2002242 |
LTE UE features for V2X |
Ericsson |
| R1-2002430 |
Summary on LTE UE features for others |
Moderator (NTT DOCOMO, INC.) |
| 7.1 |
Maintenance of Release 15 NR |
|
| R1-2002200 |
On capturing features that are mandatory without capability signaling in specifications |
Ericsson |
| R1-2002710 |
RAN1#100b-e preparation phase on NR Rel-15 CRs |
Ad-hoc chair (Samsung) |
| R1-2002723 |
RAN1#100bis-e preparation phase output on NR Rel-15 CRs |
Adhoc Chair (Samsung) |
| R1-2003131 |
Session notes for 7.1 (Maintenance of Release 15 NR) |
Ad-Hoc Chair (Samsung) |
| 7.1.1 |
Maintenance for Initial access and mobility |
|
| R1-2001608 |
Correction on RRC parameter of failureDetectionResources |
ZTE |
| R1-2001609 |
Correction on configuration of ra-searchspace |
ZTE |
| R1-2002105 |
38.213 DRAFT CR (Rel-15, F) on PRACH power ramping suspension |
Samsung |
| R1-2002106 |
38.213 DRAFT CR (Rel-16, A) on PRACH power ramping suspension |
Samsung |
| R1-2002107 |
38.211 DRAFT CR (Rel-15, F) on the calculation of k_SSB |
Samsung |
| R1-2002108 |
38.211 DRAFT CR (Rel-16, A) on the calculation of k_SSB |
Samsung |
| R1-2002109 |
38.211 DRAFT CR (Rel-15, F) on the reference for L_max |
Samsung |
| R1-2002168 |
Discussion on the QCL assumption for paging reception |
OPPO |
| R1-2002169 |
Draft CR on the QCL assumption for paging reception |
OPPO |
| R1-2002231 |
Correction on SS-RSRPB measurement |
Huawei, HiSilicon |
| 7.1.2 |
Maintenance for MIMO |
|
| R1-2001644 |
CR on PDSCH EPRE to CSIRS EPRE assumption for CQI feedback |
vivo |
| R1-2001911 |
TP for the maximum number of CSI-RS resources for BM |
LG Electronics |
| R1-2002110 |
38.214 DRAFT CR (Rel-15, F) on CSI reporting for BWP size < 24 PRBs |
Samsung |
| R1-2002111 |
38.214 DRAFT CR (Rel-16, A) on CSI reporting for BWP size < 24 PRBs |
Samsung |
| R1-2002195 |
Draft CR on SRS carrier switching for 38.212 |
ZTE |
| R1-2002196 |
Draft CR on SRS carrier switching for 38.213 |
ZTE |
| R1-2002197 |
Clarification on minimum number of supported PDSCH Resource Element mapping patterns |
Ericsson |
| R1-2002202 |
Correction on TRS configuration to TS38.214 |
CMCC |
| R1-2002290 |
PUCCH Spatial Relation after CBRA BFR |
Nokia, Nokia Shanghai Bell |
| R1-2002291 |
Clarification on the number of occupied CPUs and delay requirements for CSI reports using PUSCH |
Nokia, Nokia Shanghai Bell |
| R1-2002292 |
Clarification on which UE capability component indicates the number of supported simultaneous CSI calculations N_CPU |
Nokia, Nokia Shanghai Bell |
| R1-2002312 |
Clarifications on TRS configuration with duplexing direction change |
Apple |
| R1-2002313 |
Discussion on applicable time for PDSCH and PUSCH beam indication |
Apple |
| R1-2002314 |
Draft CR on L1-RSRP report on PUSCH |
Apple |
| R1-2002315 |
Draft CR on applicable time for PDSCH beam indication |
Apple |
| R1-2002316 |
Draft CR on applicable time for PUSCH beam indication |
Apple |
| R1-2002317 |
Draft CR on QCL assumption for DL PT-RS and DMRS |
Apple |
| R1-2002318 |
Draft CR on QCL indication for CSI-RS |
Apple |
| R1-2002491 |
Correction on CSI-RS resource set configuration |
Ericsson |
| R1-2002497 |
Correction to contention-based beam failure recovery |
Ericsson |
| R1-2002517 |
Draft CR on resource and port occupation of duplicate CSI-RS resource |
Qualcomm Incorporated |
| R1-2002518 |
Discussion on CR on resource and port occupation of duplicate CSI-RS resource |
Qualcomm Incorporated |
| R1-2002519 |
Draft CR on CSI report based on deactivated or deconfigured resources |
Qualcomm Incorporated |
| R1-2002520 |
Discussion on CSI report based on deactivated or deconfigured resources |
Qualcomm Incorporated |
| R1-2002521 |
Draft CR on type-A and Type-B Carrier Switching |
Qualcomm Incorporated |
| R1-2002522 |
Discussion paper on Type-A and Type-B Carrier Switching |
Qualcomm Incorporated |
| R1-2002764 |
CR on CSI reporting for BWP size < 24 PRBs |
Samsung, Apple, CATT, Ericsson, Fraunhofer, Huawei, HiSilicon, Interdigital, LG Electronics, Lenovo, Motorola Mobility, Nokia, NSB, NTT DOCOMO, OPPO, Qualcomm, vivo, ZTE |
| R1-2002765 |
CR on CSI reporting for BWP size < 24 PRBs |
Samsung, Apple, CATT, Ericsson, Fraunhofer, Huawei, HiSilicon, Interdigital, LG Electronics, Lenovo, Motorola Mobility, Nokia, NSB, NTT DOCOMO, OPPO, Qualcomm, vivo, ZTE |
| R1-2002828 |
LS on default RE mapping patterns |
RAN1, Ericsson |
| R1-2002904 |
CR to 38.214 clarification on resource and port occupation of duplicate CSI-RS resources |
Qualcomm Incorporated |
| R1-2002905 |
CR to 38.214 clarification on resource and port occupation of duplicate CSI-RS resources |
Qualcomm |
| R1-2002906 |
CR on L1-RSRP report on PUSCH |
Apple |
| R1-2002907 |
CR on L1-RSRP report on PUSCH |
Apple |
| 7.1.3 |
Maintenance for Scheduling/HARQ aspects |
|
| R1-2001610 |
Correction on PDCCH blind detection for NR-DC |
ZTE |
| R1-2001645 |
Clarification on UE behavior with empty list for SFI combination per cell |
vivo |
| R1-2001646 |
CR on OCC length for PUCCH format 4 |
vivo |
| R1-2001780 |
Correction on out-of-order HARQ of SPS PDSCH release |
OPPO |
| R1-2001781 |
Correction on multiplexing HARQ-ACK/SR/CSI |
OPPO |
| R1-2001982 |
Clarification on UE features on BWP operations |
Intel Corporation |
| R1-2002060 |
Clarification for processing order of UL multiplexing and cancellation |
CATT |
| R1-2002061 |
Correction on the definition for timeline condition |
CATT |
| R1-2002062 |
Correction for PUCCH repetition transmission |
CATT |
| R1-2002063 |
Clarification on PUSCH frequency hopping |
CATT |
| R1-2002223 |
Draft 38.212 CR - Specification alignment on SFI configuration |
Nokia, Nokia Shanghai Bell |
| R1-2002230 |
Correction on rate-matching for PDSCH/PDSCH with SPS in TS38.214 |
Huawei, HiSilicon |
| R1-2002379 |
Correction on rate matching output sequence length |
Sharp |
| R1-2002380 |
Correction on removal of padding bits in DCI size alignment procedure |
Sharp |
| R1-2002462 |
UL grant overridden between configured grant and RAR grant |
ASUSTeK |
| R1-2002463 |
Draft LS on UL grant overridden between configured grant and RAR grant |
ASUSTeK |
| R1-2002464 |
CR on multi-slot PUCCH repetition overlap with a single PUSCH |
ASUSTeK |
| R1-2002523 |
Draft CR on 38.214 PDSCH resource mapping |
Qualcomm Incorporated |
| R1-2002581 |
Clarification on UCI multiplexing on PUSCH |
Huawei, HiSilicon |
| R1-2002582 |
Correction on PDCCH candidate colliding with RB-symbol level RMR in TS38.213 |
Huawei, HiSilicon |
| R1-2002616 |
Correction to dynamic frequency domain resource allocation type selection |
Nokia, Nokia Shanghai Bell |
| R1-2002617 |
Draft 38.214 CR Corrections to PDSCH PRB bundling |
Nokia, Nokia Shanghai Bell |
| R1-2002629 |
Clarification on PUSCH slot-aggregation and A-CSI multiplexing |
Ericsson |
| R1-2002668 |
Corrections on multiplexing UCI from multiple PUCCHs on PUSCH. |
Huawei, HiSilicon |
| R1-2002669 |
Corrections on dynamic PUSCH skipping with overlapping with PUCCH |
Huawei, HiSilicon |
| R1-2002675 |
Correction on PDCCH blind detection capability for CA in TS38.213 |
Huawei, HiSilicon |
| R1-2002682 |
Corrections on dynamic PUSCH skipping without overlapping with PUCCH |
Huawei, HiSilicon |
| R1-2002733 |
Correction on PDCCH blind detection for NR-DC |
ZTE |
| R1-2002839 |
CR on 38.214 PDSCH resource mapping |
Qualcomm Incorporated |
| R1-2002840 |
CR on 38.214 PDSCH resource mapping |
Qualcomm Incorporated |
| R1-2002902 |
Correction on PDCCH blind detection for NR-DC |
ZTE |
| R1-2002903 |
Correction on PDCCH blind detection for NR-DC |
ZTE |
| 7.1.4 |
Maintenance for NR-LTE co-existence |
|
| R1-2002524 |
Draft CR on 36.213 ENDC single-Tx operation |
Qualcomm Incorporated |
| R1-2002525 |
Draft CR on 38.213 ENDC single-Tx operation |
Qualcomm Incorporated |
| R1-2002619 |
Correction on PUSCH and PDSCH scheduling with CSS |
Nokia, Nokia Shanghai Bell |
| R1-2002766 |
Correction on PUSCH and PDSCH scheduling with CSS |
Nokia, Nokia Shanghai Bell |
| R1-2002767 |
Correction on PUSCH and PDSCH scheduling with CSS |
Nokia, Nokia Shanghai Bell |
| 7.1.5 |
Maintenance for UL power control |
|
| R1-2002665 |
Correction on PUSCH with a Type 1 configured grant |
Huawei, HiSilicon |
| 7.1.6 |
Other |
|
| R1-2001960 |
Correction for inconsistent shadow fading parameters in NTN rural scenario |
Nokia, Nokia Shanghai Bell |
| R1-2001961 |
Correction for inconsistent shadow fading parameters in NTN rural scenario |
Nokia, Nokia Shanghai Bell |
| 7.2 |
Maintenance of Release 16 NR |
|
| R1-2002618 |
Draft 38.214 CR Correction to TBS determination when 3824
| Nokia, Nokia Shanghai Bell |
|
| R1-2002639 |
Addition of UE measurements to enable OTA conformance testing |
Keysight Technologies UK Ltd |
| R1-2003138 |
Corrections of cross-slot scheduling restriction |
Nokia, Nokia Shanghai Bell |
| R1-2003139 |
Correction of two-step RACH |
Nokia, Nokia Shanghai Bell |
| R1-2003140 |
Corrections on NR URLLC support |
Nokia, Nokia Shanghai Bell |
| R1-2003141 |
Corrections on Industrial IoT |
Nokia, Nokia Shanghai Bell |
| R1-2003142 |
Corrections of NR positioning support |
Nokia, Nokia Shanghai Bell |
| R1-2003143 |
Corrections on NR - U |
Nokia, Nokia Shanghai Bell |
| R1-2003144 |
Corrections on NR V2X |
Nokia, Nokia Shanghai Bell |
| R1-2003145 |
Corrections on Cross-carrier Scheduling with Different Numerologies |
Nokia, Nokia Shanghai Bell |
| R1-2003146 |
Corrections on NR enhanced MIMO |
Nokia, Nokia Shanghai Bell |
| R1-2003147 |
Correction on SRS-RSRP reception procedure for CLI |
Nokia, Nokia Shanghai Bell |
| R1-2003161 |
Corrections to NR-based access to unlicensed spectrum |
Ericsson |
| R1-2003162 |
Corrections to NR-based access to unlicensed spectrum |
Ericsson |
| R1-2003163 |
Corrections to NR positioning support |
Ericsson |
| R1-2003164 |
Corrections to MIMO enhancements |
Ericsson |
| R1-2003165 |
Corrections to two-step RACH |
Ericsson |
| R1-2003166 |
Corrections to cross-carrier scheduling with different numerologies |
Ericsson |
| R1-2003167 |
Corrections to V2X |
Ericsson |
| R1-2003168 |
Corrections for power saving after RAN1#100bis-e |
Huawei |
| R1-2003169 |
Corrections on 5G V2X sidelink features after RAN1#100bis-e |
Huawei |
| R1-2003170 |
Corrections in TS 38.212 for NR postioning after RAN1#100bis-e |
Huawei |
| R1-2003171 |
Miscelleanous corrections in TS 38.212 for NR MIMO after RAN1#100bis-e |
Huawei |
| R1-2003172 |
Corrections for Rel-16 MR-DC/CA after RAN1#100bis-e |
Huawei |
| R1-2003173 |
Corrections for URLLC after RAN1#100bis-e |
Huawei |
| R1-2003174 |
Corrections for Rel-16 NR-U after RAN1#100bis-e |
Huawei |
| R1-2003175 |
Corrections on integrated access and backhaul |
Samsung |
| R1-2003176 |
Corrections on Ultra Reliable Low Latency Communications Enhancements |
Samsung |
| R1-2003177 |
Corrections on UE power savings |
Samsung |
| R1-2003178 |
Corrections on Sidelink |
Samsung |
| R1-2003179 |
Corrections on Positioning |
Samsung |
| R1-2003180 |
Corrections on shared spectrum channel access |
Samsung |
| R1-2003181 |
Corrections on MIMO enhancements |
Samsung |
| R1-2003182 |
Corrections on Industrial IoT |
Samsung |
| R1-2003183 |
Corrections on NR-DC and on Cross-carrier Scheduling with Different Numerologies |
Samsung |
| R1-2003184 |
Corrections on two-step RACH |
Samsung |
| R1-2003185 |
Corrections on half-duplex operation in CA with unpaired spectrum |
Samsung |
| R1-2003186 |
Corrections to CSI-SINR definition |
Intel Corporation |
| R1-2003187 |
Correction to UL Relative Time of Arrival definition |
Intel Corporation |
| R1-2003188 |
Corrections to RSSI definition for NR-U |
Intel Corporation |
| R1-2003190 |
Updated consolidated RRC parameters list for Rel-16 NR |
Moderator (Qualcomm) |
| R1-2003191 |
LS on updated Rel-16 LTE and NR RRC parameter lists |
RAN1, Qualcomm |
| R1-2003192 |
Corrections to integrated access and backhaul for NR |
Ericsson |
| 7.2.1 |
Maintenance of Two step RACH for NR |
|
| R1-2002820 |
Editorial TPs for 2-step RACH |
Moderator (ZTE) |
| 7.2.1.1 |
Channel Structure for Two-Step RACH |
|
| R1-2001524 |
Corrections on channel structure of 2-step RACH |
Huawei, HiSilicon |
| R1-2001647 |
Remaining issues on channel structure for 2-step RACH |
vivo |
| R1-2001710 |
Remaining issues of the channel structure for 2-step RACH |
ZTE, Sanechips |
| R1-2001712 |
FL summary on the maintenance of the 2-step RACH channel structure |
Moderator (ZTE) |
| R1-2001766 |
Discussion on Channel Structure for Two-step RACH |
OPPO |
| R1-2001949 |
Remaining details of Channel Structure for 2-step RACH |
LG Electronics |
| R1-2001958 |
Discussion on Two-step RACH LS received from RAN2 |
Nokia, Nokia Shanghai Bell |
| R1-2001976 |
Discussion on Two-step RACH related LS received from RAN2 |
Nokia, Nokia Shanghai Bell |
| R1-2001983 |
Remaining details of channel structure for 2-step RACH |
Intel Corporation |
| R1-2002064 |
Remaining issues on 2-step RACH channel structure |
CATT |
| R1-2002112 |
Channel Structure for Two-Step RACH |
Samsung |
| R1-2002259 |
Remaining issue on preamble and PRU mapping for 2-step CFRA |
Spreadtrum Communications |
| R1-2002319 |
Remaining issues on channel structure for 2-step RACH |
Apple |
| R1-2002369 |
Channel Structure Related Corrections For 2-Step RACH |
Ericsson |
| R1-2002431 |
Maintenance for Channel Structure for Two-Step RACH |
NTT DOCOMO, INC. |
| R1-2002526 |
Remaining issues and clarification on channel structure for Two-Step RACH |
Qualcomm Incorporated |
| R1-2002728 |
FL summary#2 on the maintenance of the 2-step RACH channel structure |
Moderator (ZTE) |
| R1-2002816 |
Summary of email discussion [100b-e-NR-2step-RACH-01] |
Moderator (ZTE) |
| R1-2002817 |
Summary of email discussion [100b-e-NR-2step-RACH-02] |
Moderator (ZTE) |
| R1-2002818 |
Summary of email discussion [100b-e-NR-2step-RACH-03] |
Moderator (ZTE) |
| R1-2002819 |
Summary of email discussion [100b-e-NR-2step-RACH-04] |
Moderator (ZTE) |
| R1-2003019 |
Text Proposal of PRACH validation rule |
Moderator (ZTE) |
| R1-2003020 |
Text Proposal of PUSCH validation rule |
Moderator (ZTE) |
| R1-2003021 |
Text Proposal of alignment of terminology for RAR |
Moderator (ZTE) |
| R1-2003022 |
Text Proposal of UE behavior if MsgA PRACH transmission is canceled |
Moderator (ZTE) |
| R1-2003023 |
Text Proposal of clarification on the guard period between hops |
Moderator (ZTE) |
| R1-2003024 |
Text Proposal of the terminology for frequency hops |
Moderator (ZTE) |
| R1-2003025 |
Text Proposal of clarification on the DMRS sequences |
Moderator (ZTE) |
| R1-2003026 |
Text Proposal of clarification on the slot offset |
Moderator (ZTE) |
| R1-2003027 |
Text Proposals of editorial changes for 2-step RACH |
Moderator (ZTE) |
| 7.2.1.2 |
Procedure for Two-step RACH |
|
| R1-2001525 |
Corrections on procedure of 2-step RACH |
Huawei, HiSilicon |
| R1-2001648 |
Remaining issues on procedure for 2-step RACH |
vivo |
| R1-2001711 |
Remaining issues of the 2-step RACH procedures |
ZTE, Sanechips |
| R1-2001713 |
FL summary on the maintenance of the 2-step RACH procedures |
Moderator (ZTE) |
| R1-2001767 |
Remaining issues for procedure of 2-step RACH |
OPPO |
| R1-2001950 |
Remaining details of Procedure for 2-step RACH |
LG Electronics |
| R1-2001959 |
RAN1 terminology alignment for two-step RACH |
Nokia, Nokia Shanghai Bell |
| R1-2001984 |
Remaining details of procedure for 2-step RACH |
Intel Corporation |
| R1-2002065 |
Remaining issues on 2-step RACH procedure |
CATT |
| R1-2002113 |
Procedure for Two-step RACH |
Samsung |
| R1-2002260 |
Clarification on the starting point of MsgB window |
Spreadtrum Communications |
| R1-2002370 |
Procedure Related Corrections for 2-Step RACH |
Ericsson |
| R1-2002432 |
Maintenance for Procedure for Two-step RACH |
NTT DOCOMO, INC. |
| R1-2002527 |
Remaining issues on procedures for Two-Step RACH |
Qualcomm Incorporated |
| R1-2002729 |
FL summary#2 on the maintenance of the 2-step RACH procedures |
Moderator (ZTE) |
| 7.2.1.3 |
Other |
|
| R1-2001951 |
Remaining details of designing 2-step RACH for NR-U |
LG Electronics |
| R1-2002371 |
MsgA PUSCH Configuration in 2-Step CFRA |
Ericsson |
| R1-2002574 |
Further considerations on 2-step RACH |
Huawei, HiSilicon |
| 7.2.2 |
Maintenance of NR-based Access to Unlicensed Spectrum |
|
| R1-2003128 |
Maintenance of NR-based Access to Unlicensed Spectrum |
Ad-Hoc Chair (Ericsson) |
| 7.2.2.1.1 |
Initial access signals/channels |
|
| R1-2001649 |
Remaining issues on initial access signals and channles |
vivo |
| R1-2001702 |
Remaining issues on the initial access signals for NR-U |
ZTE, Sanechips |
| R1-2001756 |
Discussion on the remaining issues of initial access signal/channel |
OPPO |
| R1-2001932 |
Remaining issues of initial access signals and channels for NR-U |
LG Electronics |
| R1-2002028 |
Initial access signals and channels |
Ericsson |
| R1-2002114 |
Initial access signals and channels for NR-U |
Samsung |
| R1-2002224 |
Remaining issues on Initial Access Signals and Channels for NR-U |
Nokia, Nokia Shanghai Bell |
| R1-2002262 |
Remaining issues on initial access signals/channels |
Spreadtrum Communications |
| R1-2002575 |
Maintainance on the initial access signals and channels |
Huawei, HiSilicon |
| R1-2002734 |
FL summary for NR-U initial access signals and channels |
Moderator (Qualcomm) |
| R1-2002915 |
Summary of email discussion on k_ssb indiation |
Moderator (Qualcomm) |
| R1-2002995 |
Summary#2 of email discussion on k_ssb indiation |
Moderator (Qualcomm) |
| R1-2002997 |
Draft LS to RAN2 on restriction on ARFCN for CGI reading |
Qualcomm |
| R1-2003032 |
LS to RAN2 on restriction on ARFCN for CGI reading |
RAN1, Qualcomm |
| 7.2.2.1.2 |
DL signals and channels |
|
| R1-2001532 |
Maintainance on DL signals and channels |
Huawei, HiSilicon |
| R1-2001650 |
Remaining issues on physical DL channel design in unlicensed spectrum |
vivo |
| R1-2001703 |
Remaining issues on the DL channels for NR-U |
ZTE, Sanechips |
| R1-2001757 |
Discussion on the remaining issues of DL signals and channels |
OPPO |
| R1-2001902 |
Remaining issues on DL signals and channels for NR-U |
MediaTek Inc. |
| R1-2001933 |
Remaining issues of DL signals and channels for NR-U |
LG Electronics |
| R1-2001985 |
DL signals and channels for NR-unlicensed |
Intel Corporation |
| R1-2002029 |
DL signals and channels |
Ericsson |
| R1-2002054 |
Maintenance for DL signals and channels for NR-U |
Panasonic Corporation |
| R1-2002115 |
DL signals and channels for NR-U |
Samsung |
| R1-2002225 |
Remaining issues on DL signals and channels |
Nokia, Nokia Shanghai Bell |
| R1-2002275 |
Remaining issues in DL signals and channels |
Spreadtrum Communications |
| R1-2002320 |
Remaining issues of DL signals and channels |
Apple |
| R1-2002381 |
Remaining issues and corrections on DL signals and channels for NR-U |
Sharp |
| R1-2002528 |
TP for DL signals and channels for NR-U |
Qualcomm Incorporated |
| R1-2002630 |
Text proposal for search space group switching |
Google Inc. |
| R1-2002685 |
Feature lead summary for NR-U DL Signals and Channels |
Moderator (Lenovo) |
| R1-2002786 |
Summary of email discussion [100b-e-NR-unlic-NRU-DL_Signals_and_Channels-01] on SS group sets |
Moderator (Lenovo) |
| R1-2002787 |
Summary of email discussion [100b-e-NR-unlic-NRU-DL_Signals_and_Channels-02] on available RB set indication and COT duration |
Moderator (Lenovo) |
| R1-2002788 |
Summary of email discussion [100b-e-NR-unlic-NRU-DL_Signals_and_Channels-03] on CSI-RS |
Moderator (Lenovo) |
| R1-2002789 |
Summary of email discussion [100b-e-NR-unlic-NRU-DL_Signals_and_Channels-04] on capturing prior agreements |
Moderator (Lenovo) |
| R1-2003039 |
Draft LS on aligning RRC parameter list with TS38.213 |
Lenovo |
| R1-2003040 |
LS on aligning RRC parameter list with TS38.213 |
RAN1, Lenovo |
| R1-2003041 |
Draft TP for correcting interpretation of COT duration and available RB set indicator field |
Moderator (Lenovo) |
| R1-2003042 |
Draft TP on search space set group switching |
Moderator (Lenovo) |
| 7.2.2.1.3 |
UL signals and channels |
|
| R1-2001533 |
Maintainance on uplink signals and channels |
Huawei, HiSilicon |
| R1-2001651 |
Remaining issues on physical UL channel design in unlicensed spectrum |
vivo |
| R1-2001704 |
Remaining issues on the UL channels for NR-U |
ZTE, Sanechips |
| R1-2001758 |
Discussion on the remaining issues of UL signals and channels |
OPPO |
| R1-2001875 |
Remaining issues on UL signals and channels for NR-U |
Fujitsu |
| R1-2001903 |
Remaining issues on UL signals and channels for NR-U |
MediaTek Inc. |
| R1-2001934 |
Remaining issues of UL signals and channels for NR-U |
LG Electronics |
| R1-2001973 |
Remaining issues for UL signals and channels for NR-U |
Lenovo, Motorola Mobility |
| R1-2001986 |
UL signals and channels for NR-unlicensed |
Intel Corporation |
| R1-2002030 |
UL signals and channels |
Ericsson |
| R1-2002036 |
Feature Lead Summary for UL Signals and Channels |
Moderator (Ericsson) |
| R1-2002075 |
TP for SRS configuration |
CATT |
| R1-2002116 |
UL signals and channels for NR-U |
Samsung |
| R1-2002192 |
Remaining Issues on UL Signals and Channels for NR-U |
Nokia, Nokia Shanghai Bell |
| R1-2002246 |
UL signals and channels |
ETRI |
| R1-2002276 |
Remaining issues in UL signals and channels |
Spreadtrum Communications |
| R1-2002321 |
Remaining issues of UL signals and channels |
Apple |
| R1-2002365 |
TPs on uplink signals in NRU |
NEC |
| R1-2002382 |
Remaining issues on UL signals/channels for NR-U |
Sharp |
| R1-2002433 |
Remaining issues on UL signals and channels for NR-U |
NTT DOCOMO, INC. |
| R1-2002529 |
TP for UL signals and channels for NR-U |
Qualcomm Incorporated |
| R1-2002912 |
FL Summary for [100b-e-NR-unlic-NRU-ULSignalsChannels-01] Email discussion/approval |
Moderator (Ericsson) |
| R1-2002913 |
FL Summary for [100b-e-NR-unlic-NRU-ULSignalsChannels-02] Email discussion/approval |
Moderator (Ericsson) |
| R1-2002914 |
FL Summary for [100b-e-NR-unlic-NRU-ULSignalsChannels-03] Email discussion/approval |
Moderator (Ericsson) |
| R1-2003055 |
FL Summary#2 for [100b-e-NR-unlic-NRU-ULSignalsChannels-01] Email discussion/approval |
Moderator (Ericsson) |
| R1-2003056 |
FL Summary#2 for [100b-e-NR-unlic-NRU-ULSignalsChannels-02] Email discussion/approval |
Moderator (Ericsson) |
| R1-2003057 |
FL Summary#2 for [100b-e-NR-unlic-NRU-ULSignalsChannels-03] Email discussion/approval |
Moderator (Ericsson) |
| 7.2.2.2.1 |
Channel access procedures |
|
| R1-2001534 |
Maintainance on the channel access procedure |
Huawei, HiSilicon |
| R1-2001652 |
Remaining issues on the channel access procedures |
vivo |
| R1-2001705 |
Remaining issues on the channel access procedure for NR-U |
ZTE, Sanechips |
| R1-2001759 |
Discussion on the remaining issues of channel access procedure |
OPPO |
| R1-2001935 |
Remaining issues of channel access procedure for NR-U |
LG Electronics |
| R1-2001987 |
Channel access mechanism for NR-unlicensed |
Intel Corporation |
| R1-2002031 |
Channel access procedures |
Ericsson |
| R1-2002117 |
Channel access procedures for NR-U |
Samsung |
| R1-2002193 |
Remaining Issues on Channel Access Procedures for NR-U |
Nokia, Nokia Shanghai Bell |
| R1-2002247 |
Remaining issues on channel access procedures for NR-U |
ETRI |
| R1-2002284 |
Feature lead summary on NR-U channel access procedures |
Moderator (Nokia) |
| R1-2002383 |
Remaining issues and corrections on channel access procedure for NR-U |
Sharp |
| R1-2002405 |
Remaining issues on channel access for NR-U operation |
MediaTek Inc. |
| R1-2002434 |
Remaining issues on channel access procedures for NR-U |
NTT DOCOMO, INC. |
| R1-2002465 |
TP on shared spectrum in NR-U |
NEC |
| R1-2002530 |
TP for Channel access procedures for NR unlicensed |
Qualcomm Incorporated |
| R1-2002632 |
Remaining issues on channel access procedure for NR-U |
WILUS Inc. |
| R1-2002684 |
COT sharing information in CG-UCI |
Lenovo, Motorola Mobility |
| R1-2002751 |
Feature lead summary#2 on NR-U channel access procedures |
Moderator (Nokia) |
| R1-2002933 |
Feature lead summary#1 on email discussion [100b-e-NR-unlic-NRU-ChAcc-01] |
Moderator (Nokia) |
| R1-2002934 |
Feature lead summary#1 on email discussion [100b-e-NR-unlic-NRU-ChAcc-02] |
Moderator (Nokia) |
| R1-2003062 |
Feature lead summary#2 on email discussion [100b-e-NR-unlic-NRU-ChAcc-01] |
Moderator (Nokia) |
| R1-2003063 |
Feature lead summary#2 on email discussion [100b-e-NR-unlic-NRU-ChAcc-02] |
Moderator (Nokia) |
| 7.2.2.2.2 |
Enhancements to initial access procedure |
|
| R1-2001535 |
Maintainance on the initial access procedures |
Huawei, HiSilicon |
| R1-2001653 |
Remaining issues on initial access procedure for NR-U |
vivo |
| R1-2001701 |
Feature lead summary on NR-U enhancement to initial access procedures |
Moderator (Charter Communications, Inc) |
| R1-2001706 |
Remaining issues on the initial access procedure for NR-U |
ZTE, Sanechips |
| R1-2001760 |
Discussion on the remaining issues of enhancements to initial access procedure |
OPPO |
| R1-2001936 |
Remaining issues of initial access and mobility for NR-U |
LG Electronics |
| R1-2001988 |
Enhancements to initial access and mobility for NR-unlicensed |
Intel Corporation |
| R1-2002032 |
Enhancements to initial access procedures |
Ericsson |
| R1-2002118 |
Initial access procedures for NR-U |
Samsung |
| R1-2002248 |
Remaining issues on initial access procedure for NR-U |
ETRI |
| R1-2002263 |
Remaining issues on initial access procedure |
Spreadtrum Communications |
| R1-2002278 |
On Enhancements to Initial Access Procedures for NR-U |
Nokia, Nokia Shanghai Bell |
| R1-2002407 |
Remaining issues on initial access procedure for NR-U operation |
MediaTek Inc. |
| R1-2002531 |
TP for Initial access and mobility procedures for NR-U |
Qualcomm Incorporated |
| R1-2002849 |
Outcome of email thread [100b-e-NR-unlic-NRU-InitAccessProc-01] |
Moderator (Charter Communications) |
| R1-2002850 |
Outcome of email thread [100b-e-NR-unlic-NRU-InitAccessProc-02] |
Moderator (Charter Communications) |
| R1-2002851 |
Outcome of email thread [100b-e-NR-unlic-NRU-InitAccessProc-03] |
Moderator (Charter Communications) |
| R1-2002852 |
Summary of [100b-e-NR-unlic-NRU-InitAccessProc-04] for Reply LS on NR-U PRACH Root Sequence for 2-Step RA |
Moderator (Ericsson) |
| R1-2002853 |
LS Response on NR-U PRACH root sequence for 2-step RA |
RAN1, Ericsson |
| R1-2002916 |
Summary of email discussion on LSB of SFN validation |
Moderator (Qualcomm) |
| R1-2002992 |
LS on removing the word “candidate” in Subclause 8.1.1 of TS 38.133 v16.3.0 |
RAN1, Samsung, Charter Communications |
| R1-2002996 |
Summary#2 of email discussion on LSB of SFN validation |
Moderator (Qualcomm) |
| R1-2003044 |
LS on Signaling of Q Parameter for NR-U |
RAN1, Charter Communications |
| 7.2.2.2.3 |
HARQ enhancement |
|
| R1-2001536 |
Maintainance on HARQ-ACK enhancement |
Huawei, HiSilicon |
| R1-2001654 |
Remaining issues on HARQ operation for NR-U |
vivo |
| R1-2001707 |
Remaining issues on the HARQ for NR-U |
ZTE, Sanechips |
| R1-2001761 |
Discussion on the remaining issues of HARQ enhancements |
OPPO |
| R1-2001904 |
Remaining issues on HARQ operation for NR-U |
MediaTek Inc. |
| R1-2001937 |
Remaining issues of HARQ procedure for NR-U |
LG Electronics |
| R1-2001974 |
Remaining issues for HARQ enhancement for NR-U |
Lenovo, Motorola Mobility |
| R1-2001989 |
Enhancements to HARQ for NR-unlicensed |
Intel Corporation |
| R1-2002033 |
HARQ enhancement |
Ericsson |
| R1-2002119 |
HARQ enhancement for NR-U |
Samsung |
| R1-2002227 |
Remaining issues on NR-U HARQ scheduling and feedback |
Nokia, Nokia Shanghai Bell |
| R1-2002249 |
HARQ enhancement |
ETRI |
| R1-2002306 |
One shot HARQ ACK feedback |
InterDigital, Inc. |
| R1-2002384 |
Remaining issues and corrections on HARQ enhancement for NR-U |
Sharp |
| R1-2002532 |
TP for Enhancements to Scheduling and HARQ Operation for NR-U |
Qualcomm Incorporated |
| R1-2002631 |
Text proposal for enhanced dynamic HARQ procedures |
Google Inc. |
| R1-2002690 |
HARQ enhancement |
Ericsson |
| R1-2002696 |
Feature lead summary#1 on NR-U HARQ |
Moderator (Huawei) |
| R1-2002922 |
Feature lead summary#1 on email discussion 100b-e-NR-unlic-NRU-HARQ-01 (Type-3 HARQ-ACK codebook) |
Moderator (Huawei) |
| R1-2002923 |
Feature lead summary#1 on email discussion 100b-e-NR-unlic-NRU-HARQ-02 (Type-2 HARQ-ACK codebook) |
Moderator (Huawei) |
| R1-2002924 |
Feature lead summary#1 on email discussion 100b-e-NR-unlic-NRU-HARQ-03 (SPS) |
Moderator (Huawei) |
| R1-2003028 |
TP for NR-U HARQ issue B1 |
Moderator (Huawei) |
| R1-2003029 |
TP for NR-U HARQ issue B10 |
Moderator (Huawei) |
| R1-2003030 |
Draft TPs for NRU HARQ Issue A9 |
Moderator (Huawei) |
| R1-2003031 |
TP for NR-U HARQ issue A11 |
Moderator (Huawei) |
| 7.2.2.2.4 |
Configured grant enhancement |
|
| R1-2001537 |
Maintainance on the configured grant procedures |
Huawei, HiSilicon |
| R1-2001655 |
Remaining issues on the enhancements to configured grant |
vivo |
| R1-2001657 |
Feature lead summary on NRU configured grant enhancement |
Moderator (vivo) |
| R1-2001708 |
Remaining issues on the configured grant for NR-U |
ZTE, Sanechips |
| R1-2001762 |
Discussion on the remaining issues of configured grant enhancements |
OPPO |
| R1-2001814 |
Remaining issues on configured grant enhancement for NR-U |
Sony |
| R1-2001938 |
Remaining issues of configured grant for NR-U |
LG Electronics |
| R1-2001975 |
Remaining issues for configured grant enhancement for NR-U |
Lenovo, Motorola Mobility |
| R1-2001990 |
Enhancements to configured grants for NR-unlicensed |
Intel Corporation |
| R1-2002034 |
Configured grant enhancement |
Ericsson |
| R1-2002120 |
Configured grant enhancement for NR-U |
Samsung |
| R1-2002162 |
Clarification on NR-U configured grant enhancement |
Panasonic Corporation |
| R1-2002194 |
Remaining Issues on Configured Grant Enhancement for NR-U |
Nokia, Nokia Shanghai Bell |
| R1-2002435 |
Remaining issues on configured grant enhancement for NR-U |
NTT DOCOMO, INC. |
| R1-2002533 |
TP for Enhancements to configured grants for NR-U |
Qualcomm Incorporated |
| R1-2002633 |
Remaining issue on configured grant for NR-U |
WILUS Inc. |
| R1-2002737 |
Feature lead summary#2 on NRU configured grant enhancement |
Moderator (vivo) |
| R1-2002745 |
Summary of prep email discussion on NRU-CG |
Moderator (vivo) |
| R1-2002982 |
Feature lead summary of [100b-e-NR-unlic-NRU-CG-01] Email discussion |
Moderator (vivo) |
| R1-2002983 |
Feature lead summary of [100b-e-NR-unlic-NRU-CG-02] Email discussion |
Moderator (vivo) |
| R1-2002984 |
Editorial corrections on NRU-CG to 38.213 |
Moderator (vivo) |
| R1-2003074 |
LS to RAN2 on clarification of RVID for the first transmission for CG-PUSCH |
RAN1, Qualcomm |
| 7.2.2.2.5 |
Wide-band operation |
|
| R1-2001538 |
Maintainance on the wideband operation procedures |
Huawei, HiSilicon |
| R1-2001656 |
Remaining issues on wideband operation in NR-U |
vivo |
| R1-2001709 |
Remaining issues on the wideband operation for NR-U |
ZTE, Sanechips |
| R1-2001763 |
Discussion on the remaining issues of wide-band operations |
OPPO |
| R1-2001905 |
Remaining issues on wideband operation for NR-U |
MediaTek Inc. |
| R1-2001939 |
Remaining issues of wide-band operation for NR-U |
LG Electronics |
| R1-2001940 |
Summary on maintenance of wide-band operation for NR-U |
Moderator (LG Electronics) |
| R1-2001991 |
Wideband operation for NR-unlicensed |
Intel Corporation |
| R1-2002035 |
Wideband operation |
Ericsson |
| R1-2002121 |
Wide-band operation for NR-U |
Samsung |
| R1-2002198 |
Remaining issues on Rel-16 NR-U wideband operations |
Panasonic |
| R1-2002226 |
Remaining issues on Wideband operation in NR-U |
Nokia, Nokia Shanghai Bell |
| R1-2002277 |
Remaining issues in wide-band operation |
Spreadtrum Communications |
| R1-2002322 |
Remaining issues of wideband operation |
Apple |
| R1-2002385 |
Remaining issues on wide-band operation for NR-U |
Sharp |
| R1-2002534 |
TP for Wideband operation for NR-U operation |
Qualcomm Incorporated |
| R1-2002722 |
Summary#2 on maintenance of wide-band operation for NR-U |
Moderator (LG Electronics) |
| R1-2002754 |
Summary of email discussion [100b-e-NR-unlic-NRU-WB-01] on RB set configuration for NR-U wide-band operation |
Moderator (LG Electronics) |
| R1-2002755 |
Summary of email discussion [100b-e-NR-unlic-NRU-WB-02] on CORESET and search space configuration for NR-U wideband operation |
Moderator (LG Electronics) |
| R1-2002908 |
LS on intra-cell guard band configuration for NR-U |
RAN1, LG Electronics |
| R1-2002955 |
Summary#2 of email discussion [100b-e-NR-unlic-NRU-WB-01] on RB set configuration for NR-U wide-band operation |
Moderator (LG Electronics) |
| R1-2002956 |
Summary#2 of email discussion [100b-e-NR-unlic-NRU-WB-02] on CORESET and search space configuration for NR-U wideband operation |
Moderator (LG Electronics) |
| 7.2.2.3 |
Other |
|
| R1-2001764 |
Discussion on the other remaining issues |
OPPO |
| R1-2002576 |
Other Maintainance for NR-U |
Huawei, HiSilicon |
| 7.2.3.2 |
Extensions of RACH occasions and periodicities for backhaul RACH resources |
|
| R1-2001874 |
Remaining issues in IAB PRACH |
ZTE, Sanechips |
| R1-2002935 |
Outcome of [100b-e-NR-IAB-01] regarding TP for section 6.3.3.2 of 38.211 |
Moderator (Qualcomm) |
| 7.2.3.3 |
Mechanisms for resource multiplexing among backhaul and access links |
|
| R1-2001526 |
Remaining issues on resource multiplexing among backhaul and access links |
Huawei, HiSilicon |
| R1-2001658 |
Remaining issue on mechanisms for resource multiplexing among backhaul and access links |
vivo |
| R1-2001862 |
Remaining maintenance issues for IAB resource multiplexing |
AT&T |
| R1-2001863 |
Summary on Mechanisms for resource multiplexing among backhaul and access links |
Moderator (AT&T) |
| R1-2001882 |
Remaining issues in IAB resource multiplexing |
ZTE, Sanechips |
| R1-2001952 |
Remaining details on IAB resource multiplexing |
LG Electronics |
| R1-2002203 |
Remaining issues on mechanisms for resource multiplexing among backhaul and access links |
CMCC |
| R1-2002535 |
Remaining issues and clarifications on IAB resource management |
Qualcomm Incorporated |
| R1-2002650 |
Definition of IAB half-duplex operation in paired spectrum |
Ericsson |
| R1-2002802 |
Summary of [100b-e-NR-IAB-02] regarding IAB-MT Resource/Control Channel Configuration |
Moderator (AT&T) |
| R1-2002803 |
Summary of [100b-e-NR-IAB-03] regarding IAB Operation in Paired Spectrum |
Moderator (AT&T) |
| R1-2002954 |
Draft LS on RAN1 agreements related to resource multiplexing in IAB |
Ericsson |
| R1-2002991 |
TP for 38.213 regarding usage of tdd-UL-DL-ConfigurationDedicated-IAB-MT |
Moderator (AT&T) |
| R1-2003043 |
LS on RAN1 agreements related to resource multiplexing in IAB |
RAN1, Ericsson |
| 7.2.3.4 |
Mechanism to support the "case-1" OTA timing alignment |
|
| R1-2001527 |
Remaining issues on the "case-1" OTA timing alignment |
Huawei, HiSilicon |
| R1-2001792 |
Specifications for T_delta signalling |
Nokia, Nokia Shanghai Bell |
| R1-2001883 |
Remaining issues in IAB case-1 timing |
ZTE, Sanechips |
| R1-2001893 |
FL summary on remaining issues in IAB case-1 timing |
Moderator (ZTE) |
| R1-2001953 |
Text proposals on case 1 timing alignment |
LG Electronics |
| R1-2002436 |
Discussion on the RAN2 LS on T_delta in IAB |
NTT DOCOMO, INC |
| R1-2002536 |
Remaining issues on OTA timing |
Qualcomm Incorporated |
| R1-2002651 |
On T_delta Signaling in MAC CE |
Ericsson |
| R1-2002750 |
FL summary#2 on remaining issues in IAB case-1 timing |
Moderator (ZTE) |
| R1-2002898 |
Draft reply LS on T_delta in IAB |
ZTE |
| R1-2002931 |
Reply LS on T_delta in IAB |
RAN1, ZTE |
| 7.2.3.5 |
Other |
|
| R1-2002652 |
On max number of commonSearchSpaceListIAB |
Ericsson |
| 7.2.4 |
Maintenance for 5G V2X with NR sidelink |
|
| R1-2002053 |
TR 37.985, “Overall description of Radio Access Network (RAN) aspects for Vehicle-to-everything (V2X) based on LTE and NR”, v1.2.0 |
Huawei |
| R1-2002762 |
TR 37.985, “Overall description of Radio Access Network (RAN) aspects for Vehicle-to-everything (V2X) based on LTE and NR”, v1.2.0 |
Huawei |
| 7.2.4.1 |
Physical layer structure for sidelink |
|
| R1-2001550 |
Remaining details of sidelink physical layer structure |
Huawei, HiSilicon |
| R1-2001577 |
Remaining issues of NR sidelink physical layer structure |
ZTE, Sanechips |
| R1-2001659 |
Remaining issues on physical layer structure for NR sidelink |
vivo |
| R1-2001745 |
Draft text proposals on physical layer structure for NR-V2X |
OPPO |
| R1-2001803 |
Remaining details of Physical layer structure for sidelink |
Nokia, Nokia Shanghai Bell |
| R1-2001815 |
Remaining issues on Physical layer structure for sidelink |
Sony |
| R1-2001846 |
Discussion on sidelink physical layer structure |
MediaTek Inc. |
| R1-2001884 |
Discussion on physical layer structure for NR sidelink |
LG Electronics |
| R1-2001962 |
Physical layer structure for sidelink |
TCL Communication Ltd. |
| R1-2001967 |
Discussion on physical layer structure for NR sidelink |
Lenovo, Motorola Mobility |
| R1-2001977 |
Remaining Issues in Physical Layer Structures for NR V2X |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2001992 |
Solutions to remaining opens of physical structure for NR V2X sidelink design |
Intel Corporation |
| R1-2002039 |
Remaining details on physical layer structure for the sidelink |
Futurewei |
| R1-2002076 |
Remaining issues on physical layer structure for NR sidelink |
CATT |
| R1-2002122 |
On Physical Layer Structures for NR Sidelink |
Samsung |
| R1-2002123 |
Feature lead summary#1 for agenda item 7.2.4.1 Physical layer structure for sidelink |
Moderator (Samsung) |
| R1-2002124 |
Feature lead summary#2 for agenda item 7.2.4.1 Physical layer structure for sidelink |
Moderator (Samsung) |
| R1-2002204 |
Remaining issues on physical layer structure for sidelink |
CMCC |
| R1-2002232 |
Physical layer structure for NR sidelink |
Ericsson |
| R1-2002265 |
Remaining issues of physical layer structure for sidelink |
Spreadtrum Communications |
| R1-2002299 |
Remaining Issues on Physical Layer Structure for NR V2X |
InterDigital, Inc. |
| R1-2002323 |
On Remaining Details of NR V2X Physical Layer Structure |
Apple |
| R1-2002358 |
Remaining issue on physical layer structure for sidelink in NR V2X |
Panasonic Corporation |
| R1-2002361 |
Remaining issues on physical layer structure |
NEC |
| R1-2002386 |
Remaining issues on physical layer structure for NR sidelink |
Sharp |
| R1-2002400 |
Discussion on SCI content for 5G V2X |
Xiaomi Communications |
| R1-2002437 |
Remaining issues on sidelink physical layer structure |
NTT DOCOMO, INC. |
| R1-2002537 |
Considerations on Physical Layer aspects of NR V2X |
Qualcomm Incorporated |
| R1-2002627 |
Remaining issues of V2X PHY layer structure |
Mitsubishi Electric RCE |
| R1-2002689 |
On Physical Layer Structures for NR Sidelink |
Samsung |
| R1-2003034 |
Text Proposals for indication of MCS tables |
Moderator (Samsung) |
| R1-2003135 |
Text Proposals for indication of MCS tables |
Moderator (Samsung) |
| 7.2.4.2.1 |
Mode 1 |
|
| R1-2001551 |
Remaining details of sidelink resource allocation mode 1 |
Huawei, HiSilicon |
| R1-2001660 |
Remaining issues on mode 1 resource allocation mechanism |
vivo |
| R1-2001746 |
Remaining issues of mode 1 resource allocation for NR-V2X |
OPPO |
| R1-2001804 |
Remaining details of Resource allocation for sidelink - Mode 1 |
Nokia, Nokia Shanghai Bell |
| R1-2001876 |
Remaining issues on configured grant for NR V2X |
Fujitsu |
| R1-2001885 |
Discussion on resource allocation for Mode 1 |
LG Electronics |
| R1-2001895 |
Remaining issues of mode 1 operation on sidelink |
ZTE, Sanechips |
| R1-2001906 |
Sidelink mode-1 resource allocation |
MediaTek Inc. |
| R1-2001963 |
Resource allocation for NR sidelink Mode 1 |
TCL Communication Ltd. |
| R1-2001968 |
Discussion on resource allocation for NR sidelink Mode 1 |
Lenovo, Motorola Mobility |
| R1-2001993 |
Solutions to remaining opens of resource allocation mode-1 for NR V2X sidelink design |
Intel Corporation |
| R1-2002040 |
Remaining details on mode-1 resource allocation |
Futurewei |
| R1-2002077 |
Remaining issues on Mode 1 resource allocation in NR V2X |
CATT |
| R1-2002125 |
On Mode 1 for NR Sidelink |
Samsung |
| R1-2002184 |
Mode-1 resource allocation for NR V2X |
ITL |
| R1-2002205 |
Remaining issues on mode 1 resource allocation mechanism |
CMCC |
| R1-2002233 |
Resource Allocation Mode 1 for NR SL |
Ericsson |
| R1-2002244 |
Feature lead summary#1 on Resource allocation for NR sidelink Mode 1 |
Moderator (Ericsson) |
| R1-2002245 |
Feature lead summary#2 on Resource allocation for NR sidelink Mode 1 |
Moderator (Ericsson) |
| R1-2002266 |
Remaining issues in NR sidelink mode 1 resource allocation |
Spreadtrum Communications |
| R1-2002300 |
Remaining Issues on NR Sidelink Mode 1 Resource Allocation |
InterDigital, Inc. |
| R1-2002324 |
On Remaining Details of Mode 1 Resource Allocation |
Apple |
| R1-2002377 |
On Resource Allocation Mode 1 for NR V2X |
Convida Wireless |
| R1-2002387 |
Remaining issues on resource allocation mode 1 for NR sidelink |
Sharp |
| R1-2002401 |
On Sidelink HARQ report of V2x communications |
Xiaomi Communications |
| R1-2002438 |
Remaining issues on resource allocation mechanism mode 1 |
NTT DOCOMO, INC. |
| R1-2002466 |
Remaining issues on sidelink resource allocation mode 1 |
ASUSTeK |
| R1-2002538 |
Sidelink Resource Allocation Mode 1 |
Qualcomm Incorporated |
| R1-2002758 |
Feature lead summary#3 on Resource allocation for NR sidelink Mode 1 |
Moderator (Ericsson) |
| R1-2002821 |
Text proposal for TS 38.213 related to the agreements in [100e-NR-5G_V2X_NRSL-RA_Mode1-05] |
Moderator (Ericsson) |
| R1-2002822 |
Text proposal for TS 38.214 related to the agreements in [100e-NR-5G_V2X_NRSL-RA_Mode1-05] |
Moderator (Ericsson) |
| R1-2002848 |
LS on HARQ parameters for Mode 1 |
RAN1, Ericsson |
| R1-2002987 |
Text proposal for TS 38.213 related to the agreements in [100e-NR-5G_V2X_NRSL-RA_Mode1-05] |
Moderator (Ericsson) |
| R1-2002988 |
Text proposal for TS 38.214 related to the agreements in [100e-NR-5G_V2X_NRSL-RA_Mode1-05] |
Moderator (Ericsson) |
| R1-2003108 |
Text proposal for TS 38.213 related to the agreements in [100b-e-NR-5G_V2X_NRSL-Mode-1-02] |
Moderator (Ericsson) |
| R1-2003109 |
Text proposal for TS 38.213 related to the agreements in [100b-e-NR-5G_V2X_NRSL-Mode-1-03] |
Moderator (Ericsson) |
| R1-2003110 |
Text proposal for TS 38.212 related to the agreements in [100b-e-NR-5G_V2X_NRSL-Mode-1-04] |
Moderator (Ericsson) |
| R1-2003111 |
Text proposal for TS 38.213 related to the agreements in [100b-e-NR-5G_V2X_NRSL-Mode-1-04] |
Moderator (Ericsson) |
| 7.2.4.2.2 |
Mode 2 |
|
| R1-2001552 |
Remaining details of sidelink resource allocation mode 2 |
Huawei, HiSilicon |
| R1-2001661 |
Remaining issues on mode 2 resource allocation mechanism |
vivo |
| R1-2001749 |
Discussion on remaining open issue for mode 2 |
OPPO |
| R1-2001793 |
Remaining Issues on Sidelink Mode 2 Resource Allocation |
Panasonic Corporation |
| R1-2001805 |
Remaining details of Resource allocation for sidelink - Mode 2 |
Nokia, Nokia Shanghai Bell |
| R1-2001877 |
Remaining details on mode 2 resource allocation for NR V2X |
Fujitsu |
| R1-2001886 |
Discussion on resource allocation for Mode 2 |
LG Electronics |
| R1-2001896 |
Remaining issues of mode 2 operation on sidelink |
ZTE, Sanechips |
| R1-2001907 |
Sidelink mode-2 resource allocation |
MediaTek Inc. |
| R1-2001964 |
Resource allocation for NR sidelink Mode 2 |
TCL Communication Ltd. |
| R1-2001969 |
Discussion on resource allocation for NR sidelink Mode 2 |
Lenovo, Motorola Mobility |
| R1-2001978 |
Remaining Issues in Resource Allocation for Mode 2 NR V2X |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2001994 |
Solutions to remaining opens of resource allocation mode-2 for NR V2X sidelink design |
Intel Corporation |
| R1-2002041 |
Remianing details on mode-2 resource allocation |
Futurewei |
| R1-2002078 |
Remaining issues on Mode 2 resource allocation in NR V2X |
CATT |
| R1-2002126 |
On Mode 2 for NR Sidelink |
Samsung |
| R1-2002234 |
Resource allocation Mode 2 for NR SL |
Ericsson |
| R1-2002267 |
Remaining issues in NR sidelink mode 2 resource allocation |
Spreadtrum Communications |
| R1-2002301 |
Remaining Issues on NR Sidelink Mode 2 Resource Allocation |
InterDigital, Inc. |
| R1-2002325 |
On Remaining Details of Mode 2 Resource Allocation |
Apple |
| R1-2002362 |
Remaining issues on resource allocation Mode 2 |
NEC |
| R1-2002388 |
Remaining issues on resource allocation mode 2 for NR sidelink |
Sharp |
| R1-2002402 |
On resource reservation in Mode 2 resource allocation |
Xiaomi Communications |
| R1-2002439 |
Remaining issues on resource allocation mechanism mode 2 |
NTT DOCOMO, INC. |
| R1-2002487 |
Remain details on mode-2 resource allocation for NR V2X |
ITL |
| R1-2002489 |
Remaining issue for Mode 2 resource allocation in NR V2X |
ASUSTeK |
| R1-2002539 |
Sidelink Resource Allocation Mechanism for NR V2X |
Qualcomm Incorporated |
| R1-2002703 |
FL summary#1 of critical issues for 7.2.4.2.2 – V2X Mode 2 |
Moderator (Intel Corporation) |
| R1-2002727 |
FL summary#2 of critical issues for 7.2.4.2.2 – V2X Mode 2 |
Moderator (Intel Corporation) |
| R1-2002829 |
Outcome of [100b-e-NR-5G_V2X_NRSL-Mode-2-05] and proposed TPs |
Moderator (Intel) |
| R1-2002830 |
Outcome of [100b-e-NR-5G_V2X_NRSL-Mode-2-06] and proposed TPs |
Moderator (Intel) |
| R1-2002950 |
Outcome of [100b-e-NR-5G_V2X_NRSL-Mode-2-05] and proposed TPs |
Moderator (Intel) |
| R1-2002951 |
Outcome of [100b-e-NR-5G_V2X_NRSL-Mode-2-06] and proposed TPs |
Moderator (Intel) |
| R1-2003035 |
Outcome of [100b-e-NR-5G_V2X_NRSL-Mode-2-01] |
Moderator (Intel) |
| R1-2003036 |
Outcome of [100b-e-NR-5G_V2X_NRSL-Mode-2-02] |
Moderator (Intel) |
| R1-2003037 |
Outcome of [100b-e-NR-5G_V2X_NRSL-Mode-2-03] |
Moderator (Intel) |
| R1-2003038 |
Outcome of [100b-e-NR-5G_V2X_NRSL-Mode-2-04] |
Moderator (Intel) |
| 7.2.4.2.3 |
Other |
|
| R1-2001662 |
Remaining issues for resource allocation |
vivo |
| R1-2001750 |
On other aspects of mode 2 resource allocation |
OPPO |
| R1-2002235 |
Other outstanding resource allocation issues |
Ericsson |
| R1-2002585 |
Remaining details of pre-emption |
Huawei, HiSilicon |
| 7.2.4.3 |
Sidelink synchronization mechanism |
|
| R1-2001553 |
Remaining details of sidelink synchronization mechanisms |
Huawei, HiSilicon |
| R1-2001578 |
Remaining issues of Synchronization |
ZTE, Sanechips |
| R1-2001663 |
Remaining issues on sidelink synchronization mechanism |
vivo |
| R1-2001747 |
Remaining issues of synchronization for NR-V2X |
OPPO |
| R1-2001806 |
Remaining details of Sidelink synchronization mechanism |
Nokia, Nokia Shanghai Bell |
| R1-2001847 |
Discussion on sidelink based synchronization mechanism |
MediaTek Inc. |
| R1-2001878 |
Remaining issues on sidelink synchronization procedure |
Fujitsu |
| R1-2001887 |
Discussion on NR sidelink synchronization mechanism |
LG Electronics |
| R1-2001995 |
Solutions to remaining opens of sidelink synchronization for NR V2X design |
Intel Corporation |
| R1-2002042 |
Remaining details on synchronization for sidelink |
Futurewei |
| R1-2002079 |
Remaining issues on sidelink synchronization mechanism in NR V2X |
CATT |
| R1-2002127 |
On Synchronization Mechanisms for NR Sidelink |
Samsung |
| R1-2002206 |
Remaining issues on sidelink synchronization mechanisms |
CMCC |
| R1-2002236 |
Synchronization mechanism for NR SL |
Ericsson |
| R1-2002268 |
Remaining issues in synchronization mechanism for NR V2X |
Spreadtrum Communications |
| R1-2002326 |
On PSBCH TDD Configuration Indication |
Apple |
| R1-2002389 |
Remaining issues on synchronization mechanism for NR sidelink |
Sharp |
| R1-2002395 |
Feature lead summary#1 on AI 7.2.4.3 Sidelink synchronization mechanism |
Moderator (CATT) |
| R1-2002396 |
Feature lead summary#2 on AI 7.2.4.3 Sidelink synchronization mechanism |
Moderator (CATT) |
| R1-2002397 |
Feature lead summary#3 on AI 7.2.4.3 Sidelink synchronization mechanism |
Moderator (CATT) |
| R1-2002440 |
Remaining issues on sidelink synchronization mechanism |
NTT DOCOMO, INC. |
| R1-2002540 |
Synchronization mechanism enhancment for cluster merge |
Qualcomm Incorporated, FirstNet, UK Home office, Kyocera, Continental Automotive GmbH, LGE, AT&T, OPPO, Panasonic, Ford Motor Company, Bosch, NTT DOCOMO, Fraunhofer HHI, Fraunhofer IIS |
| R1-2002694 |
Remaining issues on sidelink synchronization mechanism in NR V2X |
CATT |
| R1-2002756 |
Synchronization mechanism enhancment for cluster merge |
Qualcomm Incorporated, FirstNet, UK Home office, Kyocera, Continental Automotive GmbH, LGE, AT&T, OPPO, Panasonic, Ford Motor Company, Bosch, NTT DOCOMO, Fraunhofer HHI, Fraunhofer IIS, Volkswagen AG |
| R1-2002990 |
LS on NR V2X Slot number determination |
RAN1, CATT |
| 7.2.4.4 |
In-device coexistence between LTE and NR sidelinks |
|
| R1-2001554 |
Remaining details of in-device coexistence between LTE and NR sidelinks |
Huawei, HiSilicon |
| R1-2001664 |
Remaining issues on In-device coexistence between NR and LTE sidelinks |
vivo |
| R1-2001751 |
Remaining open issues on in-device coexistence |
OPPO |
| R1-2001807 |
Remaining details of In-device coexistence between LTE and NR sidelinks |
Nokia, Nokia Shanghai Bell |
| R1-2001888 |
Discussion on in-device coexistence between LTE and NR sidelinks |
LG Electronics |
| R1-2001897 |
Remaining issues of in-device coexistence |
ZTE, Sanechips |
| R1-2002050 |
Remaining details on in-device coexistence between LTE and NR sidelinks |
Futurewei |
| R1-2002128 |
On In-device Coexistence between LTE and NR Sidelink |
Samsung |
| R1-2002237 |
In-device coexistence between LTE and NR sidelinks |
Ericsson |
| R1-2002541 |
Corrections for in-device coexistence between LTE and NR sidelink |
Qualcomm Incorporated |
| R1-2002709 |
Feature Lead summary of In-device Coexistence Aspects in NR-V2X |
Moderator (Qualcomm) |
| R1-2002732 |
Feature Lead summary#2 of In-device Coexistence Aspects in NR-V2X |
Moderator (Qualcomm) |
| R1-2003064 |
Text Proposals for [100b-e-NR-5G_V2X_NRSL-InDevice-Coex-01] |
Moderator (Qualcomm) |
| 7.2.4.5 |
Physical layer procedures for sidelink |
|
| R1-2001555 |
Remaining details of physical layer procedures for sidelink |
Huawei, HiSilicon |
| R1-2001665 |
Remaining issues on physical layer procedure for NR sidelink |
vivo |
| R1-2001748 |
Remaining issues of physical layer procedure for NR-V2X |
OPPO |
| R1-2001808 |
Remaining details of Physical layer procedures for sidelink |
Nokia, Nokia Shanghai Bell |
| R1-2001879 |
Remaining issues on power reduction rule for NR V2X |
Fujitsu |
| R1-2001889 |
Discussion on physical layer procedure for NR sidelink |
LG Electronics |
| R1-2001892 |
Feature lead summary#1 for AI 7.2.4.5 Physical layer procedures for sidelink |
Moderator (LG Electronics) |
| R1-2001898 |
Remaining issues on PHY procedures for Rel-16 sidelink |
ZTE, Sanechips |
| R1-2001965 |
Physical layer procedures for sidelink |
TCL Communication Ltd. |
| R1-2001970 |
Discussion on physical layer procedures for NR sidelink |
Lenovo, Motorola Mobility |
| R1-2001979 |
Remaining Issues in Physical Layer Procedures for NR V2X |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2001996 |
Solutions to remaining opens of physical layer procedures for NR V2X sidelink design |
Intel Corporation |
| R1-2002043 |
Remaining details on physical procedures for sidelink |
Futurewei |
| R1-2002080 |
Remaining issues on physical layer procedures for NR V2X |
CATT |
| R1-2002129 |
On Physical Layer Procedures for NR Sidelink |
Samsung |
| R1-2002207 |
Remaining issues on physical layer procedures for sidelink |
CMCC |
| R1-2002238 |
Physical layer procedures for NR sidelink |
Ericsson |
| R1-2002269 |
Remaining issues in physical layer procedures for sidelink |
Spreadtrum Communications |
| R1-2002302 |
Remaining Issues on Physical Layer Procedures for NR V2X |
InterDigital, Inc. |
| R1-2002327 |
On Remaining Details of Physical Layer Procedures for NR V2X Sidelink |
Apple |
| R1-2002359 |
Remaining issue on physical layer procedures for sidelink in NR V2X |
Panasonic Corporation |
| R1-2002363 |
Remaining issues on physical layer procedure |
NEC |
| R1-2002390 |
Remaining issues on physical layer procedures for NR sidelink |
Sharp |
| R1-2002441 |
Remaining issues on sidelink physical layer procedure |
NTT DOCOMO, INC. |
| R1-2002473 |
Remaining issues on sidelink physical layer procedure on NR V2X |
ASUSTeK |
| R1-2002542 |
Physical layer procedures for sidelink |
Qualcomm Incorporated |
| R1-2002759 |
Feature lead summary#2 for AI 7.2.4.5 Physical layer procedures for sidelink |
Moderator (LG Electronics) |
| R1-2002972 |
[Draft] LS on sidelink HARQ operations |
LG Electronics |
| R1-2002973 |
[Draft] LS on sidelink CSI report |
LG Electronics |
| R1-2002985 |
LS on sidelink HARQ operations |
RAN1, LG Electronics |
| R1-2002986 |
LS on sidelink CSI report |
RAN1, LG Electronics |
| R1-2003007 |
Text proposal from Email discussion thread #1 for AI 7.2.4.5 Physical layer procedures for sidelink |
Moderator (LG Electronics) |
| R1-2003008 |
Text proposal from Email discussion thread #2 for AI 7.2.4.5 Physical layer procedures for sidelink |
Moderator (LG Electronics) |
| R1-2003009 |
Text proposal from Email discussion thread #3 for AI 7.2.4.5 Physical layer procedures for sidelink |
Moderator (LG Electronics) |
| R1-2003010 |
Text proposal from Email discussion thread #4 for AI 7.2.4.5 Physical layer procedures for sidelink |
Moderator (LG Electronics) |
| 7.2.4.6 |
QoS management for sidelink |
|
| R1-2001556 |
Remaining details of QoS management for NR sidelink |
Huawei, HiSilicon |
| R1-2001666 |
Remaining issues on QoS management for sidelink |
vivo |
| R1-2001752 |
Remaining open issues on QoS |
OPPO |
| R1-2001809 |
Remaining details of QoS management for sidelink |
Nokia, Nokia Shanghai Bell |
| R1-2001890 |
Discussion on QoS management for NR sidelink |
LG Electronics |
| R1-2001899 |
Remaining issues on QoS |
ZTE, Sanechips |
| R1-2001997 |
Remaining details of QoS and congestion control for NR V2X design |
Intel Corporation |
| R1-2002044 |
Remaining details of QoS for sidelink |
Futurewei |
| R1-2002081 |
Remaining issues on QoS management in NR V2X |
CATT |
| R1-2002130 |
On QoS Management for NR Sidelink |
Samsung |
| R1-2002239 |
QoS management for NR sidelink |
Ericsson |
| R1-2002253 |
Summary#1 for AI 7.2.4.6 QoS management for sidelink |
Moderator (Nokia) |
| R1-2002254 |
Summary#2 for AI 7.2.4.6 QoS management for sidelink |
Moderator (Nokia) |
| R1-2002303 |
Remaining Issues on Congestion control and QoS Management for NR-V2X |
InterDigital, Inc. |
| R1-2002328 |
On Remaining Details of Sidelink Channel Occupancy Ratio |
Apple |
| 7.2.4.7 |
Support of NR Uu controlling LTE sidelink |
|
| R1-2001557 |
Remaining details of NR Uu control for LTE sidelink |
Huawei, HiSilicon |
| R1-2001667 |
Remaining issues on support of NR Uu controlling LTE sidelink |
vivo |
| R1-2001810 |
Remaining details of Support of NR Uu controlling LTE sidelink |
Nokia, Nokia Shanghai Bell |
| R1-2001900 |
Remaining issues on NR Uu control LTE sidelink |
ZTE, Sanechips |
| R1-2002240 |
NR UU controlling LTE sidelink transmissions |
Ericsson |
| R1-2002707 |
FL summary #1 on NR Uu scheduling LTE sidelink |
Moderator (FUTUREWEI) |
| R1-2002847 |
FL summary #2 on NR Uu scheduling LTE sidelink |
Moderator (FUTUREWEI) |
| 7.2.4.8 |
Other |
|
| R1-2001668 |
Remaining aspects for NR V2X |
vivo |
| R1-2001754 |
Discussion on priority setting for higher layer contents |
OPPO |
| R1-2002241 |
Remaining details on resource pool determination |
Ericsson |
| R1-2002543 |
Syncronisation details for NR-V2X |
Qualcomm Incorporated |
| R1-2002586 |
Remaining details of sidelink RRC Parameter List |
Huawei, HiSilicon |
| 7.2.5.1 |
PDCCH enhancements |
|
| R1-2001545 |
Corrections on PDCCH enhancement for URLLC |
Huawei, HiSilicon |
| R1-2001611 |
Remaining issues on PDCCH enhancements for NR URLLC |
ZTE |
| R1-2001669 |
PDCCH enhancements for URLLC |
vivo |
| R1-2001694 |
Maintenance of Rel-16 URLLC PDCCH enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2001773 |
PDCCH enhancements for URLLC |
OPPO |
| R1-2001784 |
Remaining Issue of PDCCH Enhancements for NR URLLC |
Ericsson |
| R1-2001813 |
Remaining Issues on PDCCH Enhancements for URLLC |
Quectel |
| R1-2001839 |
Remaining issues on PDCCH enhancements |
MediaTek Inc. |
| R1-2001919 |
Remaining issues of PDCCH enhancements for NR URLLC |
LG Electronics |
| R1-2001998 |
Remaining issues on PDCCH enhancements for URLLC |
Intel Corporation |
| R1-2002082 |
Remaining issues on PDCCH enhancements |
CATT |
| R1-2002131 |
Remaining issues for PDCCH enhancements |
Samsung |
| R1-2002255 |
Remaining issues of PDCCH enhancements for URLLC |
Spreadtrum Communications |
| R1-2002329 |
Remaining Issues on PDCCH Enhancements for eURLLC |
Apple |
| R1-2002360 |
Remaining issues on PDCCH enhancements for NR URLLC |
Panasonic Corporation |
| R1-2002391 |
Remaining issues on PDCCH enhancements for NR URLLC |
Sharp |
| R1-2002408 |
Remaining details of PDCCH Enhancements |
Motorola Mobility, Lenovo |
| R1-2002442 |
Remaining issues for PDCCH enhancements for Rel.16 URLLC |
NTT DOCOMO, INC. |
| R1-2002484 |
Remaining issue for TCI field |
ASUSTeK |
| R1-2002544 |
Remaining issues on PDCCH Enhancements for URLLC |
Qualcomm Incorporated |
| R1-2002634 |
Remaining issues on PDCCH enhancement for NR URLLC |
WILUS Inc. |
| R1-2002655 |
DCI size alignment |
Futurewei |
| R1-2002688 |
Feature lead summary#1 on PDCCH enhancements |
Moderator (Huawei) |
| R1-2002742 |
Feature lead summary#2 on PDCCH enhancements |
Moderator (Huawei) |
| R1-2003045 |
Summary of email discussion [100e-NR-L1enh_URLLC_PDCCH-01] on remaining issues on enhanced PDCCH monitoring capability |
Moderator (Huawei) |
| R1-2003046 |
Text proposal 1 for TS 38.213 Section 10.1 on agreement in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-01] |
Moderator (Huawei) |
| R1-2003047 |
Text proposal 2 for TS 38.213 Section 10 on agreement in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-01] |
Moderator (Huawei) |
| R1-2003048 |
Summary of email discussion [100e-NR-L1enh_URLLC_PDCCH-02] on remaining issues on scaling PDCCH monitoring capability |
Moderator (Huawei) |
| R1-2003049 |
Text proposal for TS 38.213 Section 10.1 on agreements in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-02] |
Moderator (Huawei) |
| R1-2003050 |
Summary of email discussion [100e-NR-L1enh_URLLC_PDCCH-03] on remaining issues on PDCCH overbooking/dropping and corrections on DCI format 0_2/1_2 |
Moderator (Huawei) |
| R1-2003051 |
Text proposal 1 for TS 38.213 Section 10.1 on agreement in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-03] |
Moderator (Huawei) |
| R1-2003052 |
Text proposal for TS 38.212 Section 7.3.1.1.3 in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-03] |
Moderator (Huawei) |
| R1-2003053 |
Text proposal for TS 38.214 Section 5.1.2.1 in [100b-e-NR-L1enh-URLLC-PDCCH enhancements-03] |
Moderator (Huawei) |
| 7.2.5.2 |
UCI enhancements |
|
| R1-2001548 |
Corrections on UCI enhancement |
Huawei, HiSilicon |
| R1-2001607 |
Discussion on remaining issues on UCI enhancement for URLLC |
Beijing Xiaomi Mobile Software |
| R1-2001612 |
Remaining issues on UL control enhancements for NR URLLC |
ZTE |
| R1-2001670 |
UCI enhancements for URLLC |
vivo |
| R1-2001695 |
Maintenance of Rel-16 URLLC UCI enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2001774 |
UCI enhancements for URLLC |
OPPO |
| R1-2001785 |
Remaining Issue of UCI Enhancements for NR URLLC |
Ericsson |
| R1-2001840 |
Remaining issues on UCI enhancements |
MediaTek Inc. |
| R1-2001871 |
Remaining issue on UCI enhancement |
Panasonic Corporation |
| R1-2001880 |
Remaining issues on UCI enhancements for URLLC |
Fujitsu |
| R1-2001920 |
Remaining issues of UCI enhancements for NR URLLC |
LG Electronics |
| R1-2001999 |
Remaining issues on UCI enhancements for URLLC |
Intel Corporation |
| R1-2002083 |
Remaining issues on UCI enhancements |
CATT |
| R1-2002132 |
Remaining issues for UCI enhancements |
Samsung |
| R1-2002208 |
Remaining issues on UCI enhancements for URLLC |
CMCC |
| R1-2002250 |
UCI enhancements |
ETRI |
| R1-2002256 |
Remaining Issues of UCI Enhancements for URLLC |
Spreadtrum Communications |
| R1-2002304 |
UCI enhancements for URLLC |
InterDigital, Inc. |
| R1-2002330 |
Remaining Issues on UCI Enhancements for eURLLC |
Apple |
| R1-2002411 |
Remaining issue on the priority of A-SRS |
ITRI |
| R1-2002443 |
Remaining issues for UCI enhancement for Rel-16 URLLC |
NTT DOCOMO, INC. |
| R1-2002500 |
Discussion on multiplexing UCI of same type on a PUSCH |
ASUSTeK |
| R1-2002545 |
Remaining issues on UCI Enhancements for URLLC |
Qualcomm Incorporated |
| R1-2002635 |
Remaining issues on UCI enhancement for NR URLLC |
WILUS Inc. |
| R1-2002695 |
Summary#1 on UCI enhancements for R16 URLLC |
Moderator (OPPO) |
| R1-2002782 |
Summary#2 on UCI enhancements for R16 URLLC |
Moderator (OPPO) |
| R1-2002783 |
Summary of email thread [100b-e-NR-L1enh_URLLC-UCI_Enh-01] |
Moderator (OPPO) |
| R1-2002784 |
Summary of email thread [100b-e-NR-L1enh_URLLC-UCI_Enh-02] |
Moderator (OPPO) |
| R1-2002785 |
Summary of email thread [100b-e-NR-L1enh_URLLC-UCI_Enh-03] |
Moderator (OPPO) |
| 7.2.5.3 |
PUSCH enhancements |
|
| R1-2001549 |
Corrections on PUSCH enhancement |
Huawei, HiSilicon |
| R1-2001613 |
Remaining issues on PUSCH enhancements for NR URLLC |
ZTE |
| R1-2001671 |
PUSCH enhancements for URLLC |
vivo |
| R1-2001696 |
Maintenance of PUSCH enhancements for Rel-16 NR URLLC |
Nokia, Nokia Shanghai Bell |
| R1-2001775 |
PUSCH enhancements for URLLC |
OPPO |
| R1-2001786 |
Remaining Issue of PUSCH Enhancements for NR URLLC |
Ericsson |
| R1-2001816 |
Remaining issues on PUSCH enhancements for URLLC |
Sony |
| R1-2001872 |
Remaining issues on URLLC PUSCH enhancement |
Panasonic Corporation |
| R1-2001881 |
Remaining issues on PUSCH enhancements for URLLC |
Fujitsu |
| R1-2001921 |
Remaining issues of PUSCH enhancements for NR URLLC |
LG Electronics |
| R1-2002000 |
Corrections on PUSCH enhancements for URLLC |
Intel Corporation |
| R1-2002084 |
Remaining issues on PUSCH enhancements |
CATT |
| R1-2002133 |
Remaining issues for PUSCH enhancements |
Samsung |
| R1-2002209 |
Remaining issues on PUSCH enhancements for URLLC |
CMCC |
| R1-2002251 |
PUSCH enhancements |
ETRI |
| R1-2002264 |
Discussion on PUSCH enhancements for URLLC |
Spreadtrum Communications |
| R1-2002305 |
PUSCH enhancements for URLLC |
InterDigital, Inc. |
| R1-2002331 |
Remaining Issues in PUSCH enhancements |
Apple |
| R1-2002332 |
Feature lead summary #1 on PUSCH enhancements for NR eURLLC (AI 7.2.5.3) |
Moderator (Apple) |
| R1-2002392 |
Remaining issues on PUSCH enhancements for NR URLLC |
Sharp |
| R1-2002403 |
Discussion on multiplexing UCI of same type on a PUSCH |
ASUSTeK |
| R1-2002409 |
UCI multiplexing in PUSCH repetition type B |
Motorola Mobility, Lenovo |
| R1-2002444 |
Remaining issues for PUSCH enhancements for Rel.16 URLLC |
NTT DOCOMO, INC. |
| R1-2002546 |
Remaining issues on PUSCH enhancements for URLLC |
Qualcomm Incorporated |
| R1-2002636 |
Remaining issues on PUSCH enhancement for NR URLLC |
WILUS Inc. |
| R1-2002731 |
Outcome of the preparation email discussion on PUSCH enhancements for NR eURLLC (AI 7.2.5.3) |
Moderator (Apple Inc.) |
| R1-2003003 |
Summary of Email discussion [100b-e-NR-L1enh-URLLC-PUSCH-01] on PUSCH enhancements for NR eURLLC (AI 7.2.5.3) |
Moderator (Apple Inc.) |
| R1-2003004 |
Summary of Email discussion [100b-e-NR-L1enh-URLLC-PUSCH-02] on PUSCH enhancements for NR eURLLC (AI 7.2.5.3) |
Moderator (Apple Inc.) |
| R1-2003005 |
Summary of Email discussion [100b-e-NR-L1enh-URLLC-PUSCH-03] on PUSCH enhancements for NR eURLLC (AI 7.2.5.3) |
Moderator (Apple Inc.) |
| R1-2003006 |
Summary of Email discussion [100b-e-NR-L1enh-URLLC-PUSCH-04] on PUSCH enhancements for NR eURLLC (AI 7.2.5.3) |
Moderator (Apple Inc.) |
| R1-2003077 |
Summary of Email discussion [100b-e-NR-L1enh-URLLC-PUSCH-01] on PUSCH enhancements for NR eURLLC (AI 7.2.5.3) |
Moderator (Apple Inc.) |
| 7.2.5.4 |
Enhancements to scheduling/HARQ |
|
| R1-2001614 |
Remaining issues on scheduling/HARQ enhancements for NR URLLC |
ZTE |
| R1-2001672 |
Enhancement for Scheduling/HARQ |
vivo |
| R1-2001700 |
Maintenance of Rel-16 URLLC scheduling/HARQ enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2001776 |
Enhancements to scheduling and HARQ |
OPPO |
| R1-2001787 |
Remaining Issue of Scheduling/HARQ for NR URLLC |
Ericsson |
| R1-2001922 |
Remaining issues of Enhancements to scheduling/HARQ for NR URLLC |
LG Electronics |
| R1-2002001 |
Remaining issues on scheduling and HARQ enhancements for URLLC |
Intel Corporation |
| R1-2002085 |
Remaining issues on out-of-order scheduling/HARQ |
CATT |
| R1-2002210 |
Remaining issues on scheduling and HARQ |
CMCC |
| R1-2002445 |
Remaining issue on scheduling and HARQ enhancements for URLLC |
NTT DOCOMO, INC. |
| R1-2002547 |
Remaining issues on scheduling/HARQ enhancements for URLLC |
Qualcomm Incorporated |
| R1-2002583 |
Corrections on operation of out-of-order |
Huawei, HiSilicon |
| R1-2002720 |
Summary of the Remaining Issues on HARQ and Scheduling Enhancements for URLLC |
Moderator (Qualcomm Incorporated) |
| R1-2003059 |
Summary for [100b-e-NR-L1enh-URLLC-Scheduling and HARQ-01] |
Moderator (Qualcomm) |
| R1-2003060 |
Summary for [100b-e-NR-L1enh-URLLC-Scheduling and HARQ-02] |
Moderator (Qualcomm) |
| 7.2.5.5 |
Enhanced inter UE Tx prioritization/multiplexing |
|
| R1-2001547 |
Corrections on UL inter-UE multiplexing |
Huawei, HiSilicon |
| R1-2001615 |
Remaining issues on UL inter-UE multiplexing between eMBB and URLLC |
ZTE |
| R1-2001673 |
UL inter UE Tx prioritization for URLLC |
vivo |
| R1-2001676 |
Summary of UL inter UE Tx prioritization for URLLC |
Moderator (vivo) |
| R1-2001697 |
Maintenance of Rel-16 URLLC Enhanced inter UE Tx prioritization/multiplexing |
Nokia, Nokia Shanghai Bell |
| R1-2001777 |
Inter UE Tx prioritization and multiplexing |
OPPO |
| R1-2001788 |
Remaining Issue of Inter-UE Prioritization and Multiplexing of UL Transmissions |
Ericsson |
| R1-2001817 |
Remaining issues on inter-UE multiplexing |
Sony |
| R1-2001841 |
Remaining issues on enhanced inter UE Tx prioritization/multiplexing |
MediaTek Inc. |
| R1-2001873 |
Remaining issue on inter-UE prioritization |
Panasonic Corporation |
| R1-2001923 |
Remaining issues of UL inter UE Tx prioritization |
LG Electronics |
| R1-2002002 |
Remaining issues on enhanced inter-UE multiplexing |
Intel Corporation |
| R1-2002086 |
Remaining issues on inter-UE UL multiplexing |
CATT |
| R1-2002134 |
Remaining issues for inter-UE multiplexing |
Samsung |
| R1-2002211 |
Remaining issues on inter UE Tx prioritization/multiplexing |
CMCC |
| R1-2002252 |
Enhanced inter UE Tx prioritization/multiplexing |
ETRI |
| R1-2002257 |
Remaining issues of enhanced inter UE Tx prioritization/multiplexing |
Spreadtrum Communications |
| R1-2002307 |
Inter-UE prioritization/multiplexing |
InterDigital, Inc. |
| R1-2002333 |
Remaining Issues on Inter-UE Cancellation for eURLLC |
Apple |
| R1-2002548 |
Remaining issues on uplink Inter-UE Tx Multiplexing and Prioritization |
Qualcomm Incorporated |
| R1-2002637 |
Remaining issues on inter-UE multiplexing for NR URLLC |
WILUS Inc. |
| R1-2002738 |
Summary#2 of UL inter UE Tx prioritization for URLLC |
Moderator (vivo) |
| R1-2002937 |
Summary of [100b-e-NR-L1enh-URLLC-InterUE-01] |
Moderator (vivo) |
| R1-2002938 |
Summary of [100b-e-NR-L1enh-URLLC-InterUE-02] |
Moderator (vivo) |
| R1-2002939 |
Summary of [100b-e-NR-L1enh-URLLC-InterUE-03] |
Moderator (vivo) |
| 7.2.5.6 |
Enhanced UL configured grant transmission |
|
| R1-2001546 |
Corrections on configured grant transmission |
Huawei, HiSilicon |
| R1-2001616 |
Remaining issues on enhancements for UL configured grant transmission |
ZTE |
| R1-2001674 |
Enhanced UL configured grant transmissions for URLLC |
vivo |
| R1-2001698 |
Maintenance of Rel-16 URLLC Configured Grant enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2001778 |
Configured grant enhancements for URLLC |
OPPO |
| R1-2001789 |
Remaining Issue of Enhancements to UL Configured Grant Transmission for NR URLLC |
Ericsson |
| R1-2001796 |
Summary of enhanced UL configured grant transmission for URLLC |
Moderator (vivo) |
| R1-2001797 |
Summary of enhanced UL configured grant transmission for URLLC |
vivo Mobile Communication Co., |
| R1-2001798 |
Summary of enhanced UL configured grant transmission for URLLC |
vivo Mobile Communication Co., |
| R1-2001799 |
Summary of enhanced UL configured grant transmission for URLLC |
vivo Mobile Communication Co., |
| R1-2001800 |
Summary of enhanced UL configured grant transmission for URLLC |
vivo Mobile Communication Co., |
| R1-2001801 |
Summary of enhanced UL configured grant transmission for URLLC |
vivo Mobile Communication Co., |
| R1-2001802 |
Summary of enhanced UL configured grant transmission for URLLC |
vivo Mobile Communication Co., |
| R1-2001811 |
Summary of enhanced UL configured grant transmission for URLLC |
vivo Mobile Communication Co., |
| R1-2001924 |
Remaining issues of Enhanced UL configured grant transmission for NR URLLC |
LG Electronics |
| R1-2002087 |
Remaining issues on enhanced UL configured grant transmission |
CATT |
| R1-2002334 |
Remaining Issues in Enhanced Configured Grant Transmission |
Apple |
| R1-2002412 |
Maintenance of UL grant Type 2 scheduling activation |
ITRI |
| R1-2002446 |
Remaining issues for enhanced Configured grant for Rel.16 URLLC |
NTT DOCOMO, INC. |
| R1-2002804 |
Summary on email discussion [100b-e-NR-L1enh-URLLC-eCG-01] |
Moderator (vivo) |
| R1-2002805 |
Summary on email discussion [100b-e-NR-L1enh-URLLC-eCG-02] |
Moderator (vivo) |
| R1-2003120 |
Text proposal for TS 38.214 Section 6.2.2 on agreement in [100b-e-NR-L1enh-URLLC-eCG-01] |
Moderator (vivo) |
| R1-2003121 |
Text proposal for TS 38.212 section 7.3.1.1.3 on agreement in [100b-e-NR-L1enh-URLLC-eCG-01] |
Moderator (vivo) |
| R1-2003122 |
Text proposal for TS 38.214, section 6.2.3 and section 6.2.3.1 on agreement in [100b-e-NR-L1enh-URLLC-eCG-01] |
Moderator (vivo) |
| R1-2003123 |
Text proposal for TS 38.212, section 7.3.1.1.2 and 7.3.1.1.3. on agreement in [100b-e-NR-L1enh-URLLC-eCG-01] |
Moderator (vivo) |
| R1-2003124 |
Text proposal for TS 38.213 section 9 on agreement in [100b-e-NR-L1enh-URLLC-eCG-02] |
Moderator (vivo) |
| R1-2003125 |
Text proposal for TS 38.213 section 10.2 on agreement in [100b-e-NR-L1enh-URLLC-eCG-02] |
Moderator (vivo) |
| 7.2.5.7 |
Other |
|
| R1-2001606 |
Discussion on remaining issues on DL SPS enhancement for URLLC |
Beijing Xiaomi Mobile Software |
| R1-2001617 |
Remaining issues on SPS enhancements |
ZTE |
| R1-2001675 |
Other issues for URLLC |
vivo |
| R1-2001699 |
Maintenance of Rel-16 URLLC/IIoT SPS enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2001779 |
DL SPS enhancement and Intra-UE multiplexing/prioritization |
OPPO |
| R1-2001790 |
Remaining Issue of DL SPS Enhancements for NR URLLC |
Ericsson |
| R1-2001842 |
Remaining issues on multiple SPS configurations |
MediaTek Inc. |
| R1-2001925 |
Remaining issues of other aspects for URLLC/IIOT |
LG Electronics |
| R1-2001926 |
Summary on maintenance of other aspects for URLLC/IIOT |
Moderator (LG Electronics) |
| R1-2002003 |
Remaining issues on enhanced DL SPS for IIoT |
Intel Corporation |
| R1-2002088 |
Remaining issues on IIoT |
CATT |
| R1-2002135 |
Remaining issues for DL SPS and PHR |
Samsung |
| R1-2002335 |
Remaining Issues in SPS enhancements |
Apple |
| R1-2002447 |
Remaining issues for SPS enhancement for Rel-16 URLLC |
NTT DOCOMO, INC. |
| R1-2002485 |
Remaining issues on DL SPS enhancements |
Asia Pacific Telecom co. Ltd |
| R1-2002549 |
Remaining issues on DL SPS for URLLC |
Qualcomm Incorporated |
| R1-2002584 |
Corrections on other aspects for URLLC/IIOT enhancements |
Huawei, HiSilicon |
| R1-2002638 |
Remaining issues on DL SPS for NR URLLC |
WILUS Inc. |
| R1-2002721 |
Summary#2 on maintenance of other aspects for URLLC/IIOT |
Moderator (LG Electronics) |
| R1-2003000 |
Outcome of [100b-e-NR-L1enh-URLLC-IIoTenh-01] |
Moderator (LG Electronics) |
| R1-2003001 |
Outcome of [100b-e-NR-L1enh-URLLC-IIoTenh-02] |
Moderator (LG Electronics) |
| R1-2003002 |
Outcome of [100b-e-NR-L1enh-URLLC-IIoTenh-03] |
Moderator (LG Electronics) |
| 7.2.6 |
Maintenance of Enhancements on MIMO for NR |
|
| R1-2002648 |
Introduction of NR ATF measurements |
Keysight Technologies UK Ltd |
| R1-2002649 |
Correction on SS-RSRPB measurement |
Keysight Technologies UK Ltd |
| R1-2002779 |
Introduction of NR ATF measurements |
Keysight Technologies, Intel |
| R1-2002831 |
Correction on SS-RSRPB measurement |
Huawei, HiSilicon |
| R1-2002832 |
Correction on SS-RSRPB measurement |
Huawei, HiSilicon |
| R1-2003134 |
Session notes for 7.2.6 (Maintenance of Enhancements on MIMO for NR) |
Ad-Hoc Chair (Samsung) |
| 7.2.6.1 |
CSI Enhancement for MU-MIMO Support |
|
| R1-2001562 |
Remaining issues on MU-CSI in R16 |
Huawei, HiSilicon |
| R1-2001595 |
Maintenance of CSI enhancement for MU-MIMO |
ZTE |
| R1-2001677 |
Discussion on remaining issues on MU CSI |
vivo |
| R1-2001725 |
Text proposals for CSI enhancements for MU-MIMO support |
OPPO |
| R1-2001912 |
Correction on enhanced Type II port selection codebook |
LG Electronics |
| R1-2002089 |
Remaining issues on CSI Enhancement for MU-MIMO |
CATT |
| R1-2002136 |
On maintenance of Rel.16 MU CSI enhancements |
Samsung |
| R1-2002137 |
Summary of offline email discussion on [100e-NR-eMIMO-MUCSI-01] follow up |
Moderator (Samsung) |
| R1-2002138 |
Feature lead summary for MU-MIMO CSI |
Moderator (Samsung) |
| R1-2002293 |
Maintenance on Rel-16 CSI enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2002336 |
Remaining issues for Rel-16 Type II CSI enhancement |
Apple |
| R1-2002410 |
Remaining issues on MU-CSI Enhancements |
Motorola Mobility, Lenovo |
| R1-2002550 |
Remaining issues on CSI enhancement for MU-MIMO support |
Qualcomm Incorporated |
| R1-2002717 |
Feature lead summary#2 for MU-MIMO CSI |
Moderator (Samsung) |
| R1-2002752 |
Feature lead summary for MU-MIMO CSI topic #1 (BWP<24) |
Moderator (Samsung) |
| R1-2002753 |
Feature lead summary for MU-MIMO CSI topic #2 (joint TP) |
Moderator (Samsung) |
| R1-2002757 |
TP for eMIMO MU-CSI topic #2: correction on PMI subband size and basis subset selection |
Samsung |
| 7.2.6.2 |
Enhancements on Multi-TRP/Panel Transmission |
|
| R1-2001563 |
Remaining issues on multi-TRP in R16 |
Huawei, HiSilicon |
| R1-2001596 |
Maintenance of multi-TRP enhancements |
ZTE |
| R1-2001678 |
Discussion on remaining issues on multi TRP operation |
vivo |
| R1-2001726 |
Text proposals for enhancements on multi-TRP and panel Transmission |
OPPO |
| R1-2001822 |
Enhancements on Multi-TRP/Panel Transmission |
MediaTek Inc. |
| R1-2001913 |
Text proposals on enhancements on multi-TRP/panel transmission |
LG Electronics |
| R1-2001971 |
Remaining issues on multi-TRP/panel transmission |
Lenovo, Motorola Mobility |
| R1-2002004 |
Corrections to multi-TRP |
Intel Corporation |
| R1-2002052 |
TP on Multi-TRP/Panel Transmission |
Futurewei |
| R1-2002090 |
Remaining issues on multi-TRP/panel transmission |
CATT |
| R1-2002139 |
On Rel.16 multi-TRP/panel transmission |
Samsung |
| R1-2002212 |
Remaining issues on multi-TRP/panel transmission |
CMCC |
| R1-2002270 |
Discussion on remaining issues for multi-TRP operation |
Spreadtrum Communications |
| R1-2002294 |
Maintenance of Rel-16 Multi-TRP operation |
Nokia, Nokia Shanghai Bell |
| R1-2002337 |
Remaining issues for Multi-TRP enhancement |
Apple |
| R1-2002364 |
Remaining issues on multi-TRP transmission |
NEC |
| R1-2002378 |
Clarification on Multi-TRP URLLC Scheme 4 |
Convida Wireless |
| R1-2002406 |
FL summary for Multi-TRP/Panel Transmission |
Moderator (OPPO) |
| R1-2002448 |
Remaining issues on multi-TRP/panel transmission |
NTT DOCOMO, INC |
| R1-2002472 |
Remaining issues on Multi-TRP/Panel Transmission |
Ericsson |
| R1-2002551 |
Multi-TRP Enhancements |
Qualcomm Incorporated |
| R1-2002730 |
FL summary#2 for Multi-TRP/Panel Transmission |
Moderator (OPPO) |
| R1-2002825 |
Text Proposal for TS 38.212 in [100b-e-NR-eMIMO-multiTRP-01] |
Moderator (OPPO) |
| R1-2002826 |
Text Proposal for TS 38.213 in [100b-e-NR-eMIMO-multiTRP-01] |
Moderator (OPPO) |
| R1-2002827 |
Text Proposal for TS 38.214 in [100b-e-NR-eMIMO-multiTRP-01] |
Moderator (OPPO) |
| R1-2002917 |
Text Proposals in [100b-e-NR-eMIMO-multiTRP-02] |
Moderator (OPPO) |
| R1-2002936 |
Summary of email thread [100b-e-NR-eMIMO-multiTRP-01] |
Moderator (OPPO) |
| R1-2002946 |
Summary of email thread [100b-e-NR-eMIMO-multiTRP-02] |
Moderator (OPPO) |
| R1-2002947 |
Text Proposal 1 in [100b-e-NR-eMIMO-multiTRP-03] |
Moderator (OPPO) |
| R1-2002948 |
Text Proposal 2 in [100b-e-NR-eMIMO-multiTRP-03] |
Moderator (OPPO) |
| R1-2002949 |
Summary of email thread [100b-e-NR-eMIMO-multiTRP-03] |
Moderator (OPPO) |
| 7.2.6.3 |
Enhancements on Multi-beam Operation |
|
| R1-2001564 |
Remaining issues on multi-beam enhancements in R16 |
Huawei, HiSilicon |
| R1-2001597 |
Maintenance of multi-beam operation |
ZTE |
| R1-2001679 |
Discussion on remaining issues on multi beam operation |
vivo |
| R1-2001727 |
Remaining issues on Multi-beam Operation Enhancement |
OPPO |
| R1-2001818 |
Remaining issues on multi-beam operation |
Sony |
| R1-2001823 |
Remaining issues on multi-beam operation |
MediaTek Inc. |
| R1-2001914 |
Remaining issues on multi beam operation |
LG Electronics |
| R1-2001915 |
FL summary#1 on Rel-16 MB1 maintenance |
Moderator (LG Electronics) |
| R1-2001972 |
Remaining issues on Scell beam failure recovery |
Lenovo, Motorola Mobility |
| R1-2002005 |
Corrections to Multi-beam Operation |
Intel Corporation |
| R1-2002091 |
On Rel.16 support for multi-beam operation |
CATT |
| R1-2002140 |
On Rel.16 support for multibeam operation |
Samsung |
| R1-2002213 |
Remaining issues on multi-beam operation |
CMCC |
| R1-2002271 |
Discussion on remaining issues on multi-beam operation |
Spreadtrum Communications |
| R1-2002283 |
Enhancements on multi-beam operation |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2002295 |
Maintenance of Rel-16 Beam Management |
Nokia, Nokia Shanghai Bell |
| R1-2002338 |
Remaining issues on beam management enhancement |
Apple |
| R1-2002339 |
Feature Lead Summary #1 on L1-SINR and SCell BFR |
Moderator (Apple) |
| R1-2002340 |
Feature Lead Summary #2 on L1-SINR and SCell BFR |
Moderator (Apple) |
| R1-2002449 |
Remaining issues on multi-beam operation |
NTT DOCOMO, INC |
| R1-2002498 |
On the timing for pathloss RS activation |
Ericsson, Nokia |
| R1-2002552 |
Enhancements on Multi-beam Operation |
Qualcomm Incorporated |
| R1-2002725 |
FL summary#2 on Rel-16 MB1 maintenance |
Moderator (LG Electronics) |
| R1-2002810 |
Outcome of email thread [100b-e-NR-eMIMO-MB1-01] |
Moderator (LG Electronics) |
| R1-2002811 |
Outcome of email thread [100b-e-NR-eMIMO-MB1-02] |
Moderator (LG Electronics) |
| R1-2002812 |
Outcome of email thread [100b-e-NR-eMIMO-MB1-03] |
Moderator (LG Electronics) |
| R1-2002823 |
Text Proposals from Email Thread [100b-e-NR-eMIMO-MB2-01] |
Moderator (Apple) |
| R1-2002824 |
Text Proposals from Email Thread [100b-e-NR-eMIMO-MB2-03] |
Moderator (Apple) |
| R1-2002843 |
TP for capturing outcome of email thread [100b-e-NR-eMIMO-MB1-01] |
Moderator (LG Electronics) |
| R1-2002844 |
TP for capturing outcome of email thread [100b-e-NR-eMIMO-MB1-02] |
Moderator (LG Electronics) |
| R1-2002845 |
TP for capturing outcome of email thread [100b-e-NR-eMIMO-MB1-03] |
Moderator (LG Electronics) |
| R1-2002967 |
Reply LS on the application timing for pathloss RS activated/updated by MAC-CE |
RAN1, LG Electronics |
| 7.2.6.4 |
Full TX Power UL transmission |
|
| R1-2001565 |
Remaining issues on UL full power transmission in R16 |
Huawei, HiSilicon |
| R1-2001598 |
Maintenance of full power UL transmission |
ZTE |
| R1-2001680 |
Discussion on remaining issues on UL full power transmission |
vivo |
| R1-2001719 |
Feature lead summary on ULFPTx |
Moderator (vivo) |
| R1-2001728 |
Text proposals for full TX power UL transmission |
OPPO |
| R1-2001824 |
Remaining issues on UL full power transmission |
MediaTek Inc. |
| R1-2001916 |
Text proposals on full Tx power UL transmission |
LG Electronics |
| R1-2002006 |
Correction to Full Tx Power UL Transmission |
Intel Corporation |
| R1-2002092 |
Remaining issues on UL full power transmission |
CATT |
| R1-2002141 |
On UL full power transmission |
Samsung |
| R1-2002214 |
Discussion on full TX power UL transmission |
CMCC |
| R1-2002272 |
Discussion on remaining issues on full TX power for UL transmission |
Spreadtrum Communications |
| R1-2002296 |
Maintenance of Rel-16 Full TX Power UL transmission |
Nokia, Nokia Shanghai Bell |
| R1-2002341 |
Remaining issues for UL Full Power transmission enhancement |
Apple |
| R1-2002368 |
Corrections for Full Power UL Transmission |
Ericsson |
| R1-2002450 |
Remaining issue on full Tx power UL transmission |
NTT DOCOMO, INC |
| R1-2002553 |
Remaining issues on full power UL transmission |
Qualcomm Incorporated |
| R1-2002718 |
Feature lead summary#2 on ULFPTx |
Moderator (vivo) |
| R1-2002746 |
Summary of prep email discussion on ULFPTx |
Moderator (vivo) |
| R1-2002978 |
Feature lead summary of [100b-e-NR-eMIMO-ULFPTx-01] Email discussion |
Moderator (vivo) |
| R1-2002979 |
Feature lead summary of [100b-e-NR-eMIMO-ULFPTx-02] Email discussion |
Moderator (vivo) |
| R1-2002980 |
Feature lead summary of [100b-e-NR-eMIMO-ULFPTx-03] Email discussion |
Moderator (vivo) |
| R1-2002981 |
Editorial corrections on UL full power transmission |
Moderator (vivo) |
| 7.2.6.5 |
Low PAPR RS |
|
| R1-2001566 |
Discussion on low PAPR sequence in R16 |
Huawei, HiSilicon |
| R1-2001599 |
Maintenance of low PAPR RS |
ZTE |
| R1-2001681 |
Discussion on remaining issues on low PAPR RS |
vivo |
| R1-2001729 |
Text proposals for low PAPR RS |
OPPO |
| R1-2001812 |
Corrections in low PAPR RS for pi/2 BPSK PUSCH |
Indian Institute of Tech (H) |
| R1-2001825 |
Maintenance of low PAPR RS |
MediaTek Inc. |
| R1-2001908 |
Remaining issues on low PAPR RS |
Ericsson |
| R1-2002007 |
Low PAPR RS |
Intel Corporation |
| R1-2002273 |
Discussion on remaining issues on Low PAPR DMRS sequence |
Spreadtrum Communications |
| R1-2002297 |
Maintenance on Rel-16 Low PAPR RS |
Nokia, Nokia Shanghai Bell |
| R1-2002554 |
Remaining issues on low PAPR RS |
Qualcomm Incorporated |
| R1-2002693 |
Feature lead summary of low PAPR RS |
Moderator (Ericsson) |
| R1-2002726 |
Feature lead summary#2 of low PAPR RS |
Moderator (Ericsson) |
| R1-2002791 |
Maintenance of low PAPR RS |
ZTE |
| R1-2002977 |
Text proposals for issue #1 of low PAPR RS |
Moderator – (Ericsson) |
| 7.2.6.6 |
Other |
|
| R1-2001730 |
Remaining issues on multi-TRP and panel Transmission |
OPPO |
| R1-2001917 |
TP for the maximum number of CSI-RS resources for BM |
LG Electronics |
| R1-2001918 |
Critical MIMO issue from observations in the field |
Ericsson |
| R1-2002342 |
On further MIMO enhancement |
Apple |
| R1-2002467 |
On limitations of PDSCH reliable transmission |
vivo |
| R1-2002468 |
On limitations of PDSCH reliable transmission |
vivo |
| R1-2002469 |
On limitations of PDSCH reliable transmission |
vivo |
| R1-2002470 |
On limitations of PDSCH reliable transmission |
vivo |
| R1-2002471 |
On limitations of PDSCH reliable transmission |
vivo |
| R1-2002667 |
Other open issues for Rel-16 MIMO |
Huawei, HiSilicon |
| 7.2.7.1 |
PDCCH-based power saving signal/channel |
|
| R1-2001539 |
Remaining issues on PDCCH based power saving |
Huawei, HiSilicon |
| R1-2001583 |
Remaining issues on WUS PDCCH |
ZTE |
| R1-2001682 |
Maintenance of PDCCH-based power saving signal |
vivo |
| R1-2001768 |
Remaining issues for Power saving signal |
OPPO |
| R1-2001819 |
Remaining issues on PDCCH-based WUS |
Sony |
| R1-2001843 |
Remaining issues on PDCCH-based power saving signal |
MediaTek Inc. |
| R1-2001943 |
Remaining issues on PDCCH-based power saving signal/channel |
LG Electronics |
| R1-2002008 |
Remaining details of PDCCH-based power saving signal/channel |
Intel Corporation |
| R1-2002093 |
Remaining issues on the Power Saving Signals/Channels |
CATT |
| R1-2002142 |
Remaining issues for PDCCH-based power saving signal |
Samsung |
| R1-2002189 |
TP to address RAN2 LS on DCP |
NEC |
| R1-2002215 |
Remaining issues on minimum time gap for PDCCH-based power saving signal/channel |
CMCC |
| R1-2002218 |
On open issues related to DCI format 2_6 |
Nokia, Nokia Shanghai Bell |
| R1-2002261 |
Clarification on power saving signal |
Spreadtrum Communications |
| R1-2002366 |
Remaining Issues for PDCCH-based Power Saving Signal/Channel |
InterDigital |
| R1-2002414 |
Remaining issues for WUS |
Ericsson |
| R1-2002451 |
Maintenance for PDCCH-based power saving signal/channel |
NTT DOCOMO, INC. |
| R1-2002555 |
Remaining issues for PDCCH-based power saving channel |
Qualcomm Incorporated |
| R1-2002698 |
Summary#1 of AI-7.2.7.1 PDCCH-based power saving signal/channel |
Moderator (CATT) |
| R1-2003067 |
Final summary of PDCCH-based Power Saving Signal/Channel |
Moderator (CATT) |
| R1-2003068 |
Reply LS on DCP |
RAN1, CATT |
| 7.2.7.2 |
Procedure of cross-slot scheduling power saving techniques |
|
| R1-2001540 |
Remaining issues on cross-slot scheduling based power saving |
Huawei, HiSilicon |
| R1-2001584 |
Remaining issues on cross-slot scheduling power saving techniques |
ZTE |
| R1-2001683 |
Maintenance of procedure of cross-slot scheduling power saving techniques |
vivo |
| R1-2001769 |
Remaining issues for cross-slot scheduling |
OPPO |
| R1-2001820 |
Remaining issues on cross-slot scheduling for UE power saving |
Sony |
| R1-2001844 |
Remaining issues on cross-slot scheduling adaptation |
MediaTek Inc. |
| R1-2001944 |
Remaining issues on procedure of cross-slot scheduling power saving techniques |
LG Electronics |
| R1-2002009 |
Remaining details of cross-slot scheduling power saving techniques |
Intel Corporation |
| R1-2002094 |
Remaining issues on Power saving scheme with cross-slot scheduling |
CATT |
| R1-2002143 |
Remaining issues for cross-slot scheduling power saving techniques |
Samsung |
| R1-2002216 |
Remaining issues on cross-slot scheduling adaptation in cross-BWP scheduling |
CMCC |
| R1-2002219 |
Procedure of cross-slot scheduling power saving techniques |
Nokia, Nokia Shanghai Bell |
| R1-2002258 |
Remaining issues on cross-slot scheduling |
Spreadtrum Communications |
| R1-2002343 |
Remaining Issues on Cross-Slot Power Save |
Apple |
| R1-2002367 |
Remaining Issues for Cross-Slot Scheduling for UE Power Saving |
InterDigital |
| R1-2002415 |
Remaining issues for cross-slot scheduling |
Ericsson |
| R1-2002452 |
Maintenance for procedure of cross-slot scheduling power saving techniques |
NTT DOCOMO, INC. |
| R1-2002556 |
Remaining issues in cross-slot scheduling power saving |
Qualcomm Incorporated |
| R1-2002697 |
Summary#1 for Procedure of cross-slot scheduling power saving techniques |
Moderator (MediaTek) |
| R1-2002763 |
Summary#2 for Procedure of cross-slot scheduling power saving techniques |
Moderator (MediaTek) |
| 7.2.7.3 |
UE adaptation to maximum number of MIMO layers |
|
| R1-2001541 |
Remaining issues on UE adaptation to maximum MIMO layers |
Huawei, HiSilicon |
| R1-2001585 |
On UE adaptation to maximum number of MIMO layers |
ZTE |
| R1-2002220 |
On open issues for per-BWP DL MIMO layers |
Nokia, Nokia Shanghai Bell |
| R1-2002416 |
Remaining issues for MIMO layer signaling per BWP |
Ericsson |
| R1-2002702 |
Summary of UE adaptation to maximum number of MIMO layers |
Moderator (vivo) |
| 7.2.7.4 |
Other |
|
| R1-2001586 |
Views on power saving enhancement |
ZTE |
| R1-2001684 |
Other issues for R16 UE power saving |
vivo |
| R1-2002417 |
UE power saving using search space set switching |
Ericsson |
| R1-2002577 |
Other Remaining issues for Rel-16 Power saving |
Huawei, HiSilicon |
| 7.2.8 |
Maintenance of NR positioning support |
|
| R1-2003129 |
Maintenance of NR positioning support |
Ad-Hoc Chair (Ericsson) |
| 7.2.8.1 |
DL Reference Signals for NR Positioning |
|
| R1-2001558 |
Maintenance of DL PRS for NR positioning |
Huawei, HiSilicon |
| R1-2001600 |
Maintenance of DL reference signals for NR positioning |
ZTE |
| R1-2001685 |
Discussion on remaining issues on DL RS for NR positioning |
vivo |
| R1-2001731 |
Remaining Issues on DL Positioning Reference Signal |
OPPO |
| R1-2001954 |
Remaining details of DL Reference signals for NR positioning |
LG Electronics |
| R1-2002046 |
Remaining details on DL Reference Signals |
Futurewei |
| R1-2002095 |
Remaining issues on DL PRS for NR Positioning |
CATT |
| R1-2002144 |
DL Reference Signals for NR Positioning |
Samsung |
| R1-2002288 |
Corrections to DL reference signals for NR positioning |
Intel Corporation |
| R1-2002557 |
Discussion on DL PRS processing & related UE capabilities |
Qualcomm Incorporated |
| R1-2002620 |
Maintenance of rel16 DL reference signals for NR positioning |
Ericsson |
| R1-2002708 |
FL summary #1 for AI 7.2.8 – DL Reference Signals for NR Positioning |
Moderator (Intel Corporation) |
| R1-2002770 |
Summary of the RAN1 WG e-mail discussion [100b-e-NR-Pos-01] |
Moderator (Intel Corporation) |
| R1-2002771 |
Summary of the RAN1 WG e-mail discussion [100b-e-NR-Pos-02] |
Moderator (Intel Corporation) |
| 7.2.8.2 |
UL Reference Signals for NR Positioning |
|
| R1-2001559 |
Maintenance of SRS for NR positioning |
Huawei, HiSilicon |
| R1-2001601 |
Maintenance of UL reference signals for NR positioning |
ZTE |
| R1-2001686 |
Discussion on remaining issues on UL RS for NR positioning |
vivo |
| R1-2001732 |
Remaining Issues on UL Positioning Reference Signal |
OPPO |
| R1-2002038 |
Maintenance on UL reference signals for NR Positioning |
Nokia, Nokia Shanghai Bell |
| R1-2002047 |
Remaining details on UL Reference Signals |
Futurewei |
| R1-2002096 |
Remaining issues on UL SRS for NR Positioning |
CATT |
| R1-2002145 |
UL Reference Signals for NR Positioning |
Samsung |
| R1-2002199 |
Discussion on staggered SRS for NR Positioning |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2002286 |
Corrections to UL reference signals for NR positioning |
Intel Corporation |
| R1-2002621 |
Maintenance of rel16 UL reference signals for NR positioning |
Ericsson |
| R1-2002715 |
Feature lead summary for UL Reference Signals for NR Positioning |
Moderator (Ericsson) |
| R1-2002833 |
Output of email discussion [100b-e-NR-Pos-03] on UL SRS for positioning and UL RTOA reference time |
Moderator (Ericsson) |
| R1-2002970 |
Output of email discussion [100b-e-NR-Pos-03] on UL SRS for positioning and UL RTOA reference time |
Moderator (Ericsson) |
| R1-2003054 |
LS on UL RTOA reference time |
RAN1, Ericsson |
| R1-2003061 |
TPs and remaining open issues from email discussion [100b-e-NR-Pos-03] on UL SRS for positioning and UL RTOA reference time |
Moderator (Ericsson) |
| R1-2003136 |
TPs and remaining open issues from email discussion [100b-e-NR-Pos-03] on UL SRS for positioning and UL RTOA reference time |
Moderator (Ericsson) |
| 7.2.8.3 |
UE and gNB measurements for NR Positioning |
|
| R1-2001560 |
Maintenance of NR positioning measurements |
Huawei, HiSilicon |
| R1-2001602 |
Maintenance of UE and gNB measurements for NR positioning |
ZTE |
| R1-2001733 |
Remaining Issues on Measurements for NR Positioning |
OPPO |
| R1-2002048 |
Remaining details on Measurements |
Futurewei |
| R1-2002097 |
Remaining issues on NR Positioning Measurements |
CATT |
| R1-2002146 |
UE and gNB measurements for NR Positioning |
Samsung |
| R1-2002622 |
Maintenance of rel16 UE and gNB measurements for NR Positioning |
Ericsson |
| R1-2002716 |
FL Summary of Remaining issues on NR Positioning Measurements |
Moderator (CATT) |
| 7.2.8.4 |
Physical-layer procedures to support UE/gNB measurements |
|
| R1-2001561 |
Maintenance of physical layer procedures to support positioning measurements |
Huawei, HiSilicon |
| R1-2001603 |
Maintenance of physical-layer procedure for NR positioning |
ZTE |
| R1-2001687 |
Discussion on remaining issues on physical-layer procedures for NR positioning |
vivo |
| R1-2001734 |
Remaining Issues on Physical Layer Procedures for NR Positioning |
OPPO |
| R1-2001955 |
Remaining details of physical-layer procedure to support UE/gNB measurements |
LG Electronics |
| R1-2002049 |
Remaining details on Measurement Procedures |
Futurewei |
| R1-2002098 |
Remaining issues on NR Positioning Procedures |
CATT |
| R1-2002147 |
Physical-layer procedures to support UE/gNB measurements |
Samsung |
| R1-2002217 |
Remaining issues on physical layer procedure for UL SRS transmission |
CMCC |
| R1-2002287 |
Corrections to physical layer procedures for NR positioning |
Intel Corporation |
| R1-2002623 |
Maintenance of rel16 Physical-layer procedures to support UE - gNB measurements |
Ericsson |
| R1-2002713 |
Summary of 7.2.8.4: Physical-layer procedures to support UE/gNB measurements |
Moderator (Qualcomm Incorporated) |
| R1-2002989 |
Summary of Email Discussion [100b-e-NR-Pos-04] |
Moderator (Qualcomm Incorporated) |
| R1-2003069 |
LS on criterion of pathloss measurement failure for power control of SRS for positioning |
RAN1, CATT |
| 7.2.8.5 |
Other |
|
| R1-2001735 |
Discussion on RE mapping in reference signal for NR positioning |
OPPO |
| R1-2002676 |
On positioning latency and aperiodic SRS |
Huawei, HiSilicon |
| 7.2.9 |
Maintenance of NR Mobility Enhancements |
|
| R1-2002010 |
Issue Summary for NR Mobility Enhancements |
Moderator (Intel Corporation) |
| R1-2003130 |
Maintenance of NR Mobility Enhancements |
Ad-Hoc Chair (Ericsson) |
| 7.2.9.1 |
Physical Layer Aspects for Mobility Enhancements during HO and SCG Change |
|
| R1-2001530 |
Remaining issues on DAPS-HO |
Huawei, HiSilicon |
| R1-2001624 |
Remaining issues on NR mobility enhancements in physical layer |
ZTE |
| R1-2002011 |
Corrections to Physical layer aspects of NR mobility enhancement |
Intel Corporation |
| R1-2002148 |
Remaining issues for NR Mobility Enhancement |
Samsung |
| R1-2002221 |
Remaining physical layer aspects of dual active protocol stack based HO |
Nokia, Nokia Shanghai Bell |
| R1-2002344 |
On remaining issues on NR mobility enhancements |
Apple |
| R1-2002490 |
Correction to UL power sharing for DAPS HO |
Ericsson |
| R1-2002558 |
Maintenance for NR mobility enhancements |
Qualcomm Incorporated |
| R1-2002806 |
Summary of email discussions for [100b-e-NR-Mob-Enh-01] |
Moderator (Intel Corporation) |
| R1-2002807 |
Summary of email discussions for [100b-e-NR-Mob-Enh-02] |
Moderator (Intel Corporation) |
| R1-2002808 |
Summary of email discussions for [100b-e-NR-Mob-Enh-03] |
Moderator (Intel Corporation) |
| R1-2002809 |
[draft] LS on Simultaneous reception of DL signals in intra-frequency DAPS HO |
Intel Corporation |
| R1-2003058 |
LS on Simultaneous reception of DL signals in intra-frequency DAPS HO |
RAN1, Intel Corporation |
| R1-2003076 |
Draft CR on UL transmission cancellation for UL DAPS HO |
Intel Corporation |
| R1-2003137 |
Draft CR on UL transmission cancellation for UL DAPS HO |
Intel Corporation |
| 7.2.9.2 |
Other |
|
| R1-2001531 |
Remaining PHY aspects for CHO |
Huawei, HiSilicon |
| R1-2001625 |
Discussion on FR2 mobility interruption enhancements |
ZTE |
| 7.2.10.1 |
Uplink Power Control for Supporting NR-NR Dual-Connectivity |
|
| R1-2001528 |
UL power control for NR-NR dual connectivity |
Huawei, HiSilicon |
| R1-2001618 |
Remaining Issues of Dynamic Power Sharing for NR-DC |
ZTE |
| R1-2001688 |
Remaining issues on uplink power control for NR-NR DC |
vivo |
| R1-2001736 |
Text proposals for UL Power Sharing for NR-DC |
OPPO |
| R1-2002012 |
Remaining issues on uplink power control for NN-DC |
Intel Corporation |
| R1-2002345 |
Remaining issues of UL Power Control for NN-DC |
Apple |
| R1-2002346 |
Feature lead summary #1 on UL Power Control for NN-DC |
Moderator (Apple) |
| R1-2002418 |
Remaining issues for NR-DC UL Power Control |
Ericsson |
| R1-2002607 |
Remaining details of Rel-16 DC uplink power control |
Nokia, Nokia Shanghai Bell |
| R1-2002743 |
Outcome of preparation discussion on UL Power Control for NN-DC |
Moderator (Apple) |
| R1-2002744 |
Feature lead summary#2 of UL Power Control for NN-DC |
Moderator (Apple) |
| R1-2003011 |
Outcome of Phase-2 discussion on UL Power Control for NN-DC |
Moderator (Apple) |
| 7.2.10.2 |
Potential Enhancements to Single Tx Switched Uplink Solution for EN-DC |
|
| R1-2001529 |
Enhancements for single UL operation for EN-DC |
Huawei, HiSilicon |
| R1-2001619 |
Remaining Issues on Single Tx Switched Uplink Solution for EN-DC |
ZTE |
| R1-2001835 |
Remaining issues on single Tx switched UL solution for EN-DC |
MediaTek Inc. |
| R1-2002347 |
Remaining issues on single Tx operation for EN-DC |
Apple |
| R1-2002348 |
Feature lead summary #1 on single Tx operation for EN-DC |
Moderator (Apple) |
| R1-2002419 |
Remaining issues for single Tx UL enhancements |
Ericsson |
| R1-2002559 |
Remaining issues for EN-DC Single-Tx TDM Operation |
Qualcomm Incorporated |
| R1-2002608 |
Remaining details on Enhancements to Single Tx Switched Uplink Solution for EN-DC |
Nokia, Nokia Shanghai Bell |
| R1-2002999 |
Summary of email discussion [100b-e-NR- LTE_NR_DC_CA-SingleTx-01] |
Moderator (Apple) |
| 7.2.10.3 |
Support of efficient and low latency serving cell configuration/activation/setup |
|
| R1-2001542 |
Remaining issues on SCell dormancy indication |
Huawei, HiSilicon |
| R1-2001620 |
Remaining Issues on Fast SCell Activation |
ZTE |
| R1-2001689 |
Remaining issues on Scell dormancy like behavior |
vivo |
| R1-2001770 |
Discussion on remaining issues of Scell dormancy |
OPPO |
| R1-2002013 |
Remaining issues on SCell dormancy behavior |
Intel Corporation |
| R1-2002066 |
Discussion on SCell Dormancy when DCI format 2_6 is not detected |
CATT |
| R1-2002149 |
Remaining issues on dormancy Scell |
Samsung |
| R1-2002185 |
Remaining issues on SCell dormancy behavior |
MediaTek Inc. |
| R1-2002228 |
Remaining issues on Efficient CA design |
Nokia, Nokia Shanghai Bell |
| R1-2002420 |
Remaining issues for reduced latency Scell management for NR CA |
Ericsson |
| R1-2002421 |
Summary of efficient and low latency serving cell configuration/activation/setup |
Moderator (Ericsson) |
| R1-2002560 |
Remaining issues for SCell dormancy |
Qualcomm Incorporated |
| R1-2002739 |
Summary of efficient and low latency serving cell configuration/activation/setup |
Moderator (Ericsson) |
| R1-2003012 |
Summary of email discussion [100b-e-NR- LTE_NR_DC_CA-ScellDormancy-01] |
Moderator (Ericsson) |
| R1-2003013 |
Summary of email discussion [100b-e-NR- LTE_NR_DC_CA-ScellDormancy-02] |
Moderator (Ericsson) |
| 7.2.10.4 |
Support of aperiodic CSI-RS triggering with different numerology between CSI-RS and triggering PDCCH |
|
| R1-2001543 |
Remaining issues on the A-CSI RS triggering with different numerology |
Huawei, HiSilicon |
| R1-2001690 |
Remaining issues on aperiodic CSI-RS triggering |
vivo |
| R1-2001737 |
Text proposals for aperiodic CSI-RS triggering with different numerologies |
OPPO |
| R1-2001836 |
Remaining issues on X-carrier ACSI-RS triggering with different SCS |
MediaTek Inc. |
| R1-2002496 |
Correction to aperiodic CSI-RS triggering with mixed numerology |
Ericsson |
| R1-2002561 |
Remaining issues for aperiodic CSI-RS triggering with different numerology |
Qualcomm Incorporated |
| R1-2002611 |
FL summary on aperiodic CSI-RS triggering with different numerology between CSI-RS and triggering PDCCH |
Moderator (Nokia) |
| R1-2002612 |
FL summary #2 on aperiodic CSI-RS triggering with different numerology between CSI-RS and triggering PDCCH |
Moderator (Nokia) |
| R1-2002841 |
FL summary #3 on aperiodic CSI-RS triggering with different numerology between CSI-RS and triggering PDCCH |
Moderator (Nokia) |
| 7.2.10.5 |
Support of unaligned frame boundary with slot alignment and partial SFN alignment for R16 NR inter-band CA |
|
| R1-2001621 |
Remaining Issues on ASync CA |
ZTE |
| R1-2001691 |
Remaining issues on unaligned frame boundary for CA |
vivo |
| R1-2002201 |
FL summary on support of unaligned frame boundary for R16 NR inter-band CA |
Moderator (CMCC) |
| R1-2002422 |
Remaining issues for inter-band CA with unaligned frame boundary |
Ericsson |
| R1-2002475 |
Remaining issues on support of unaligned frame boundary with slot alignment |
ASUSTeK |
| R1-2002579 |
Remaining issues on intra-band CA with unaligned frame boundary |
Huawei, HiSilicon |
| R1-2002609 |
Maintanence of unaligned frame boundary with slot alignment and partial SFN alignment for inter-band CA |
Nokia, Nokia Shanghai Bell |
| R1-2002780 |
TP following the outcome of [100b-e-NR-LTE_NR_DC_CA_enh –Unaligned_CA-01] |
Moderator (CMCC) |
| R1-2002781 |
Outcome of [100b-e-NR-LTE_NR_DC_CA_enh –Unaligned_CA-02] |
Moderator (CMCC) |
| 7.2.10.6 |
Support of cross-carrier scheduling with different numerology |
|
| R1-2001622 |
Remaining Issues on Cross-carrier Scheduling with Mixed Numerologies |
ZTE |
| R1-2001692 |
Remaining issues on cross-carrier scheduling with mix numerologies |
vivo |
| R1-2001837 |
Remaining issues on X-carrier scheduling with different SCS |
MediaTek Inc. |
| R1-2001942 |
Remaining issue on cross-carrier scheduling with different numerology |
LG Electronics |
| R1-2002014 |
Remaining issues on cross-carrier scheduling with different numerology |
Intel Corporation |
| R1-2002067 |
Discussion on HARQ-ACK feedback for SPS PDSCH release with cross-carrier scheduling |
CATT |
| R1-2002423 |
Remaining issues for cross-carrier scheduling with different numerologies |
Ericsson |
| R1-2002580 |
Remaining issues on cross-carrier scheduling with different numerology |
Huawei, HiSilicon |
| R1-2002610 |
Maintenance of cross-carrier scheduling with different numerology |
Nokia, Nokia Shanghai Bell |
| R1-2002613 |
FL summary on cross-carrier scheduling with different numerology |
Moderator (Nokia) |
| R1-2002614 |
FL summary #2 on cross-carrier scheduling with different numerology |
Moderator (Nokia) |
| R1-2002711 |
Remaining issue on cross-carrier scheduling with different numerology |
LG Electronics |
| R1-2002842 |
FL summary #3 on cross-carrier scheduling with different numerology |
Moderator (Nokia) |
| 7.2.10.7 |
Other |
|
| R1-2001544 |
Discussion on Cross-carrier triggering PDCCH order |
Huawei, HiSilicon |
| R1-2001623 |
Discussion on the PUCCH group configuration for NR-DC |
ZTE |
| R1-2002424 |
Data rate handling for intra-FR NR-DC |
Ericsson |
| 7.2.11 |
NR Rel-16 UE Features |
|
| R1-2003072 |
LS on Rel-16 RAN1 UE features lists for NR |
RAN1, AT&T, NTT DOCOMO |
| R1-2003073 |
RAN1 UE features list for Rel-16 NR after RAN1#100bis-E |
Moderators (AT&T, NTT DOCOMO) |
| R1-2003205 |
void |
ETSI MCC |
| 7.2.11.1 |
UE features for two-step RACH |
|
| R1-2001714 |
Discussion on the UE features for two-step RACH |
ZTE, Sanechips |
| R1-2002015 |
Discussion on UE features for two-step RACH |
Intel Corporation |
| R1-2002068 |
Discussion of NR Rel-16 UE features for two-step RACH |
CATT |
| R1-2002150 |
UE features for two-step RACH |
Samsung |
| R1-2002349 |
Views on NR 2-step RACH UE feature |
Apple |
| R1-2002372 |
UE Features for Two-Step RACH |
Ericsson |
| R1-2002453 |
Summary on UE features for two-step RACH |
Moderator (NTT DOCOMO, INC.) |
| R1-2002562 |
Discussion on two step RACH UE features |
Qualcomm Incorporated |
| R1-2002588 |
Rel-16 UE features for 2-step RACH |
Huawei, HiSilicon |
| R1-2002860 |
Summary on Email discussion [100b-e-NR-UEFeatures-2Step-01] |
Moderator (NTT DOCOMO) |
| R1-2002861 |
Summary on Email discussion [100b-e-NR-UEFeatures-2Step-02] |
Moderator (NTT DOCOMO) |
| R1-2003197 |
Summary on email discussion [100b-e-NR-UEFeatures-Remaining] NR_2step_RACH |
Moderator (NTT DOCOMO, INC.) |
| 7.2.11.2 |
UE features for NR-U |
|
| R1-2001715 |
Discussion on the UE features for NR-U |
ZTE, Sanechips |
| R1-2001720 |
Discussion on Rel-16 NRU UE features |
vivo |
| R1-2001765 |
Discussion on UE feature for NRU |
OPPO |
| R1-2001826 |
Views on Rel-16 UE features for NR-U |
MediaTek Inc. |
| R1-2001941 |
Discussion on UE features for NR-U |
LG Electronics |
| R1-2002016 |
UE features for NR-U |
Intel Corporation |
| R1-2002037 |
UE features for NR-U |
Ericsson |
| R1-2002151 |
UE features for NR-U |
Samsung |
| R1-2002350 |
Discussions on NR-U UE features |
Apple |
| R1-2002393 |
Discussion on UE feature for NR-U |
Sharp |
| R1-2002458 |
Summary on UE features for NR-U |
Moderator (NTT DOCOMO, INC.) |
| R1-2002480 |
On UE features NR Unlicensed |
Nokia, Nokia Shanghai Bell |
| R1-2002563 |
Discussion on NR-U UE features |
Qualcomm Incorporated |
| R1-2002589 |
Rel-16 UE features for NR-U |
Huawei, HiSilicon |
| R1-2002683 |
UE Features for NR-U |
TCL Communications |
| R1-2002862 |
Summary on Email discussion [100b-e-NR-UEFeatures-NRU-01] |
Moderator (NTT DOCOMO) |
| R1-2002863 |
Summary on Email discussion [100b-e-NR-UEFeatures-NRU-02] |
Moderator (NTT DOCOMO) |
| R1-2002864 |
Summary on Email discussion [100b-e-NR-UEFeatures-NRU-03] |
Moderator (NTT DOCOMO) |
| R1-2002865 |
Summary on Email discussion [100b-e-NR-UEFeatures-NRU-04] |
Moderator (NTT DOCOMO) |
| R1-2002866 |
Summary on Email discussion [100b-e-NR-UEFeatures-NRU-05] |
Moderator (NTT DOCOMO) |
| R1-2002867 |
Summary on Email discussion [100b-e-NR-UEFeatures-NRU-06] |
Moderator (NTT DOCOMO) |
| R1-2003198 |
Summary on email discussion [100b-e-NR-UEFeatures-Remaining] NR-unlicensed |
Moderator (NTT DOCOMO, INC.) |
| 7.2.11.3 |
UE features for IAB |
|
| R1-2001861 |
Views on NR Rel-16 IAB Features |
AT&T |
| R1-2001866 |
Summary on UE features for IAB |
Moderator (AT&T) |
| R1-2001894 |
Discussion on NR Rel-16 IAB MT features |
ZTE, Sanechips |
| R1-2002017 |
Discussion on UE features for IAB |
Intel Corporation |
| R1-2002152 |
UE features for IAB |
Samsung |
| R1-2002188 |
Discussion on RAN1 UE feature for NR IAB |
LG Electronics |
| R1-2002564 |
Discussion on IAB UE features |
Qualcomm Incorporated |
| R1-2002590 |
Rel-16 UE features for IAB |
Huawei, HiSilicon |
| R1-2002653 |
Needed features for operator deployed IAB nodes |
Ericsson |
| R1-2002968 |
[Draft] LS on IAB-DU features |
Qualcomm |
| R1-2003086 |
Summary of Email Approval [100b-e-NR-UEFeatures-IAB-01] |
Moderator (AT&T) |
| R1-2003087 |
Summary of Email Approval [100b-e-NR-UEFeatures-IAB-02] |
Moderator (AT&T) |
| R1-2003088 |
Summary of Email Approval [100b-e-NR-UEFeatures-IAB-03] |
Moderator (AT&T) |
| R1-2003089 |
Summary of Email Approval [100b-e-NR-UEFeatures-IAB-04] |
Moderator (AT&T) |
| R1-2003149 |
LS on IAB-DU features |
RAN1, Qualcomm |
| 7.2.11.4 |
UE features for 5G V2X |
|
| R1-2001579 |
Discussion on Rel-16 5G_V2X_NRSL UE Features |
ZTE, Sanechips |
| R1-2001753 |
Discussion on UE feature list for Release16 5G-V2X |
OPPO |
| R1-2001783 |
Discussion on 5G V2X UE features |
vivo |
| R1-2001827 |
Views on Rel-16 UE features for NR V2X |
MediaTek Inc. |
| R1-2001867 |
Summary on UE features for 5G V2X |
Moderator (AT&T) |
| R1-2001891 |
Discussion on NR Rel-16 UE features for 5G V2X |
LG Electronics |
| R1-2002018 |
Input to discussion on UE features for NR-V2X |
Intel Corporation |
| R1-2002045 |
Features for Rel-16 V2X |
Futurewei |
| R1-2002069 |
Discussion of UE features for NR V2X |
CATT |
| R1-2002153 |
UE features for NR V2X |
Samsung |
| R1-2002243 |
UE features for 5G V2X |
Ericsson |
| R1-2002351 |
On NR UE V2X Features |
Apple |
| R1-2002398 |
UE features for 5G V2X |
Panasonic Corporation |
| R1-2002483 |
On UE features for 5G V2X |
Nokia, Nokia Shanghai Bell |
| R1-2002565 |
Discussion on V2X UE features |
Qualcomm Incorporated |
| R1-2002666 |
Rel-16 UE features for 5G V2X |
Huawei, HiSilicon |
| R1-2002790 |
[Draft] LS on LTE V2X capabilities in NR V2X |
Huawei |
| R1-2002930 |
LS on LTE V2X capabilities in NR V2X |
RAN1, Huawei |
| R1-2003078 |
Chairman's Notes of AI 7.2.11.4 |
Ad-Hoc Chair (AT&T) |
| R1-2003090 |
Summary of Email Approval [100b-e-NR-UEFeatures-V2X-01] |
Moderator (AT&T) |
| R1-2003091 |
Summary of Email Approval [100b-e-NR-UEFeatures-V2X-02] |
Moderator (AT&T) |
| R1-2003092 |
Summary of Email Approval [100b-e-NR-UEFeatures-V2X-03] |
Moderator (AT&T) |
| R1-2003093 |
Summary of Email Approval [100b-e-NR-UEFeatures-V2X-04] |
Moderator (AT&T) |
| R1-2003193 |
Summary of Email Approval [100e-b-NR-UEFeatures-Remaining] — 5G V2X with NR Sidelink Aspects |
Moderator (AT&T) |
| 7.2.11.5 |
UE features for URLLC/IIoT |
|
| R1-2001632 |
Discussion on UE feature for URLLC/IIoT |
ZTE |
| R1-2001721 |
Discussion on Rel-16 URLLC/IIOT UE features |
vivo |
| R1-2001782 |
Discussion on UE features for URLLC/IIoT |
OPPO |
| R1-2001791 |
On UE Features for URLLC and IIoT |
Ericsson |
| R1-2001795 |
UE features for URLLC |
China Unicom |
| R1-2001828 |
Views on Rel-16 UE features for NR URLLC/IIoT |
MediaTek Inc. |
| R1-2001927 |
Discussion on UE features for URLLC/IIoT |
LG Electronics |
| R1-2002019 |
On UE features for Rel-16 eURLLC and IIoT |
Intel Corporation |
| R1-2002070 |
Discussion of UE features for NR URLLC/IIoT |
CATT |
| R1-2002154 |
UE features for URLLC/IIoT |
Samsung |
| R1-2002352 |
Discussions on UE Features for URLLC/IIoT |
Apple |
| R1-2002399 |
UE features for URLLC/IIoT |
Panasonic Corporation |
| R1-2002459 |
Summary on UE features for URLLC/IIoT |
Moderator (NTT DOCOMO, INC.) |
| R1-2002482 |
On UE features for URLLC/IIOT |
Nokia, Nokia Shanghai Bell |
| R1-2002566 |
Discussion on eURLLC and IIOT UE features |
Qualcomm Incorporated |
| R1-2002591 |
Rel-16 UE features for URLLC |
Huawei, HiSilicon |
| R1-2002868 |
Summary on Email discussion [100b-e-NR-UEFeatures-URLLC/IIoT-01] |
Moderator (NTT DOCOMO) |
| R1-2002869 |
Summary on Email discussion [100b-e-NR-UEFeatures-URLLC/IIoT-02] |
Moderator (NTT DOCOMO) |
| R1-2002870 |
Summary on Email discussion [100b-e-NR-UEFeatures-URLLC/IIoT-03] |
Moderator (NTT DOCOMO) |
| R1-2002871 |
Summary on Email discussion [100b-e-NR-UEFeatures-URLLC/IIoT-04] |
Moderator (NTT DOCOMO) |
| R1-2002872 |
Summary on Email discussion [100b-e-NR-UEFeatures-URLLC/IIoT-05] |
Moderator (NTT DOCOMO) |
| R1-2002873 |
Summary on Email discussion [100b-e-NR-UEFeatures-URLLC/IIoT-06] |
Moderator (NTT DOCOMO) |
| R1-2002874 |
Summary on Email discussion [100b-e-NR-UEFeatures-URLLC/IIoT-07] |
Moderator (NTT DOCOMO) |
| R1-2002875 |
Summary on Email discussion [100b-e-NR-UEFeatures-URLLC/IIoT-08] |
Moderator (NTT DOCOMO) |
| R1-2002876 |
Summary on Email discussion [100b-e-NR-UEFeatures-URLLC/IIoT-09] |
Moderator (NTT DOCOMO) |
| R1-2002877 |
Summary on Email discussion [100b-e-NR-UEFeatures-URLLC/IIoT-10] |
Moderator (NTT DOCOMO) |
| R1-2003199 |
Summary on email discussion [100b-e-NR-UEFeatures-Remaining] NR_L1enh_URLLC |
Moderator (NTT DOCOMO, INC.) |
| R1-2003200 |
Summary on email discussion [100b-e-NR-UEFeatures-Remaining] NR_IIoT |
Moderator (NTT DOCOMO, INC.) |
| 7.2.11.6 |
UE features for eMIMO |
|
| R1-2001604 |
NR eMIMO UE features |
ZTE |
| R1-2001722 |
Discussion on Rel-16 eMIMO UE features |
vivo |
| R1-2001738 |
Discussion on Rel-16 eMIMO UE features |
OPPO |
| R1-2001794 |
UE features for MIMO |
China Unicom |
| R1-2001829 |
Views on Rel-16 UE features for NR eMIMO |
MediaTek Inc. |
| R1-2001868 |
Summary on UE features for eMIMO |
Moderator (AT&T) |
| R1-2002020 |
UE features for NR eMIMO |
Intel Corporation |
| R1-2002071 |
Discussion of UE features for NR MIMO |
CATT |
| R1-2002155 |
UE features for eMIMO |
Samsung |
| R1-2002161 |
Discussion on RAN1 UE feature for NR eMIMO |
LG Electronics |
| R1-2002274 |
Discussions on UE features for eMIMO |
Spreadtrum Communications |
| R1-2002353 |
Views on Rel-16 eMIMO UE feature list |
Apple |
| R1-2002476 |
On UE features for eMIMO |
Nokia, Nokia Shanghai Bell |
| R1-2002494 |
eMIMO UE features |
Ericsson |
| R1-2002499 |
Discussion on UE features for eMIMO |
CMCC |
| R1-2002567 |
Discussion on eMIMO UE features |
Qualcomm Incorporated |
| R1-2002592 |
Rel-16 UE features for MIMO |
Huawei, HiSilicon |
| R1-2002628 |
Discussion on UE capability issues |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2003079 |
Chairman's Notes of AI 7.2.11.6 |
Ad-Hoc Chair (AT&T) |
| R1-2003094 |
Summary of Email Approval [100b-e-NR-UEFeatures-eMIMO-01] |
Moderator (AT&T) |
| R1-2003095 |
Summary of Email Approval [100b-e-NR-UEFeatures-eMIMO-02] |
Moderator (AT&T) |
| R1-2003096 |
Summary of Email Approval [100b-e-NR-UEFeatures-eMIMO-03] |
Moderator (AT&T) |
| R1-2003097 |
Summary of Email Approval [100b-e-NR-UEFeatures-eMIMO-04] |
Moderator (AT&T) |
| R1-2003098 |
Summary of Email Approval [100b-e-NR-UEFeatures-eMIMO-05] |
Moderator (AT&T) |
| R1-2003194 |
Summary of Email Approval [100e-b-NR-UEFeatures-Remaining] — MIMO Enhancement Aspects |
Moderator (AT&T) |
| 7.2.11.7 |
UE features for UE power savings |
|
| R1-2001587 |
Discussion on UE feature for UE power saving |
ZTE |
| R1-2001772 |
Discussion on Power Saving related UE features |
OPPO |
| R1-2001830 |
Views on Rel-16 UE features for NR UE power savings |
MediaTek Inc. |
| R1-2001869 |
Summary on UE features for UE power savings |
Moderator (AT&T) |
| R1-2002021 |
On UE features for Rel-16 UE Power Saving |
Intel Corporation |
| R1-2002072 |
Discussion of UE features for NR UE power savings |
CATT |
| R1-2002425 |
Discussion on UE features for UEPS |
Ericsson |
| R1-2002481 |
On UE features for UE Power Savings |
Nokia, Nokia Shanghai Bell |
| R1-2002568 |
Discussion on power saving UE features |
Qualcomm Incorporated |
| R1-2002593 |
Rel-16 UE features for UE power saving |
Huawei, HiSilicon |
| R1-2002625 |
Discussion on Rel-16 UE power saving UE features |
vivo |
| R1-2003099 |
Summary of Email Approval [100b-e-NR-UEFeatures-PowSav-01] |
Moderator (AT&T) |
| R1-2003100 |
Summary of Email Approval [100b-e-NR-UEFeatures-PowSav-02] |
Moderator (AT&T) |
| R1-2003101 |
Summary of Email Approval [100b-e-NR-UEFeatures-PowSav-03] |
Moderator (AT&T) |
| R1-2003102 |
Summary of Email Approval [100b-e-NR-UEFeatures-PowSav-04] |
Moderator (AT&T) |
| R1-2003103 |
Summary of Email Approval [100b-e-NR-UEFeatures-PowSav-05] |
Moderator (AT&T) |
| R1-2003195 |
Summary of Email Approval [100e-b-NR-UEFeatures-Remaining] — UE Power Saving Aspects |
Moderator (AT&T) |
| 7.2.11.8 |
UE features for NR positioning |
|
| R1-2001605 |
NR positioning UE features |
ZTE |
| R1-2001723 |
Discussion on UE features for Rel-16 NR positioning |
vivo |
| R1-2001739 |
Discussion on UE features for NR Positioning |
OPPO |
| R1-2001831 |
Views on Rel-16 UE features for NR positioning |
MediaTek Inc. |
| R1-2001956 |
Discussion on UE features for NR positioning |
LG Electronics |
| R1-2002022 |
Input to discussion on UE features for NR Positioning |
Intel Corporation |
| R1-2002073 |
Discussion of UE features for NR positioning |
CATT |
| R1-2002156 |
UE features for NR positioning |
Samsung |
| R1-2002460 |
Summary on UE features for NR positioning |
Moderator (NTT DOCOMO, INC.) |
| R1-2002479 |
On UE features for NR Positioning |
Nokia, Nokia Shanghai Bell |
| R1-2002569 |
Discussion on NR Positionign UE features |
Qualcomm Incorporated |
| R1-2002587 |
Rel-16 UE features for NR positioning |
Huawei, HiSilicon |
| R1-2002624 |
View on UE feature description for NR positioning |
Ericsson |
| R1-2002712 |
Rel-16 UE features for NR positioning |
Huawei, HiSilicon |
| R1-2002878 |
Summary on Email discussion [100b-e-NR-UEFeatures-Positioning-01] |
Moderator (NTT DOCOMO) |
| R1-2002879 |
Summary on Email discussion [100b-e-NR-UEFeatures-Positioning-02] |
Moderator (NTT DOCOMO) |
| R1-2002880 |
Summary on Email discussion [100b-e-NR-UEFeatures-Positioning-03] |
Moderator (NTT DOCOMO) |
| R1-2002881 |
Summary on Email discussion [100b-e-NR-UEFeatures-Positioning-04] |
Moderator (NTT DOCOMO) |
| R1-2002882 |
Summary on Email discussion [100b-e-NR-UEFeatures-Positioning-05] |
Moderator (NTT DOCOMO) |
| R1-2003201 |
Summary on email discussion [100b-e-NR-UEFeatures-Remaining] NR positioning |
Moderator (NTT DOCOMO, INC.) |
| 7.2.11.9 |
UE features for NR mobility enhancements |
|
| R1-2001633 |
Discussion on UE feature for NR mobility enhancements |
ZTE |
| R1-2001832 |
Views on Rel-16 UE features for NR mobility enhancements |
MediaTek Inc. |
| R1-2001870 |
Summary on UE features for NR mobility enhancements |
Moderator (AT&T) |
| R1-2002023 |
UE feature for NR Mobility Enhancement |
Intel Corporation |
| R1-2002157 |
UE features for NR mobility enhancement |
Samsung |
| R1-2002354 |
Views on NR mobility ehancement UE feature |
Apple |
| R1-2002478 |
On UE features for NR Mobility Enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2002495 |
Mobility UE features |
Ericsson |
| R1-2002570 |
Discussion on Mobility Enhancements UE features |
Qualcomm Incorporated |
| R1-2002594 |
Rel-16 UE features for mobility enhancement |
Huawei, HiSilicon |
| R1-2003080 |
Chairman's Notes of AI 7.2.11.9 |
Ad-Hoc Chair (AT&T) |
| R1-2003104 |
Summary of Email Approval [100b-e-NR-UEFeatures-Mobility-01] |
Moderator (AT&T |
| R1-2003105 |
Summary of Email Approval [100b-e-NR-UEFeatures-Mobility-02] |
Moderator (AT&T) |
| R1-2003106 |
Summary of Email Approval [100b-e-NR-UEFeatures-Mobility-03] |
Moderator (AT&T) |
| R1-2003107 |
Summary of Email Approval [100b-e-NR-UEFeatures-Mobility-04] |
Moderator (AT&T) |
| 7.2.11.10 |
UE features for MR-DC/CA |
|
| R1-2001631 |
Discussion on UE feature for MR-DC CA |
ZTE |
| R1-2001833 |
Views on Rel-16 UE features for MR-DC/CA |
MediaTek Inc. |
| R1-2002024 |
UE feature for MR-DC |
Intel Corporation |
| R1-2002426 |
Discussion on UE features for MR-DC |
Ericsson |
| R1-2002454 |
Summary on UE features for MR-DC/CA |
Moderator (NTT DOCOMO, INC.) |
| R1-2002477 |
On UE features for MR-DC/CA |
Nokia, Nokia Shanghai Bell |
| R1-2002571 |
Discussion on UE features for MR-DC/CA |
Qualcomm Incorporated |
| R1-2002595 |
Rel-16 UE features for MR-DC/CA |
Huawei, HiSilicon |
| R1-2002883 |
Summary on Email discussion [100b-e-NR-UEFeatures-MRDCCA-01] |
Moderator (NTT DOCOMO) |
| R1-2002884 |
Summary on Email discussion [100b-e-NR-UEFeatures-MRDCCA-02] |
Moderator (NTT DOCOMO) |
| R1-2002885 |
Summary on Email discussion [100b-e-NR-UEFeatures-MRDCCA-03] |
Moderator (NTT DOCOMO) |
| R1-2002886 |
Summary on Email discussion [100b-e-NR-UEFeatures-MRDCCA-04] |
Moderator (NTT DOCOMO) |
| R1-2002887 |
Summary on Email discussion [100b-e-NR-UEFeatures-MRDCCA-05] |
Moderator (NTT DOCOMO) |
| R1-2003202 |
Summary on email discussion [100b-e-NR-UEFeatures-Remaining] MR-DC/CA enhancement |
Moderator (NTT DOCOMO, INC.) |
| 7.2.11.11 |
UE features for CLI/RIM |
|
| R1-2001588 |
Discussion on UE feature for CLI |
ZTE |
| R1-2001740 |
Discussion on UE features for CLI/RIM |
OPPO |
| R1-2002158 |
UE features for CLI/RIM |
Samsung |
| R1-2002279 |
UE features for CLI/RIM |
Ericsson |
| R1-2002404 |
Discussion on Rel-16 CLI UE features |
vivo |
| R1-2002455 |
Summary on UE features for CLI/RIM |
Moderator (NTT DOCOMO, INC.) |
| R1-2002488 |
On UE features for CLI/RIM |
Nokia, Nokia Shanghai Bell |
| R1-2002572 |
Discussion on UE features for CLI |
Qualcomm Incorporated |
| R1-2002596 |
Rel-16 UE features for CLI/RIM |
Huawei, HiSilicon |
| R1-2002686 |
UE features for CLI/RIM |
Intel Corporation |
| R1-2002888 |
Summary on Email discussion [100b-e-NR-UEFeatures-CLIRIM-01] |
Moderator (NTT DOCOMO) |
| R1-2003203 |
Summary on email discussion [100b-e-NR-UEFeatures-Remaining] NR_CLI_RIM |
Moderator (NTT DOCOMO, INC.) |
| 7.2.11.12 |
UE features for TEIs |
|
| R1-2001724 |
Discussion on UE TEI feature 14-7 |
vivo |
| R1-2001741 |
Discussion on Rel-16 UE features for TEIs |
OPPO |
| R1-2001834 |
Views on Rel-16 UE features for NR TEIs |
MediaTek Inc. |
| R1-2002025 |
UE features for NR TEI |
Intel Corporation |
| R1-2002280 |
UE features for TEIs |
Ericsson |
| R1-2002456 |
Summary on UE features for TEIs |
Moderator (NTT DOCOMO, INC.) |
| R1-2002573 |
Discussion on UE features for TEI |
Qualcomm Incorporated |
| R1-2002597 |
Rel-16 UE features for TEIs |
Huawei, HiSilicon |
| R1-2002889 |
Summary on Email discussion [100b-e-NR-UEFeatures-TEIs-01] |
Moderator (NTT DOCOMO) |
| R1-2002890 |
Summary on Email discussion [100b-e-NR-UEFeatures-TEIs-02] |
Moderator (NTT DOCOMO) |
| R1-2003204 |
Summary on email discussion [100b-e-NR-UEFeatures-Remaining] NR TEI |
Moderator (NTT DOCOMO, INC.) |
| 7.2.11.13 |
Other |
|
| R1-2001634 |
Remaining issues on Rel-16 NR UE features |
ZTE |
| R1-2001742 |
Discussion on the support of SRS transmission in all symbols of a slot |
OPPO |
| R1-2002026 |
On UE feature list |
Intel Corporation |
| R1-2002159 |
UE features for other aspects |
Samsung |
| R1-2002281 |
Potential change/update on existing UE features for Rel-16 UE |
Ericsson |
| R1-2002457 |
Summary on NR UE features for others |
Moderator (NTT DOCOMO, INC.) |
| R1-2002656 |
High-level discussion on Rel-16 UE features |
Futurewei |
| R1-2002674 |
Other aspects of Rel-16 UE features |
Huawei, HiSilicon |
| R1-2002687 |
Discussion on UE features |
Qualcomm Incorporated |
| R1-2002891 |
Summary on Email discussion [100b-e-NR-UEFeatures-Others-01] |
Moderator (NTT DOCOMO) |
| R1-2002892 |
Summary on Email discussion [100b-e-NR-UEFeatures-Others-02] |
Moderator (NTT DOCOMO) |
| 7.2.12 |
Other |
|
| R1-2001589 |
Discussion on CLI and TBS ambiguity |
ZTE |
| R1-2001957 |
Remaining details of CLI measurement and reporting at a UE |
LG Electronics |
| R1-2002027 |
Maintenance of aperiodic CSI-RS triggering with beam switching timing of 224 and 336 |
Intel Corporation |
| R1-2002074 |
Remaining issues of half-duplex operation in CA |
CATT |
| R1-2002170 |
On TRS muting for NR coexistence with a narrow band system |
MediaTek Inc. |
| R1-2002229 |
On remaining NR TEI issues |
Nokia, Nokia Shanghai Bell |
| R1-2002282 |
Remaining issues for Rel-16 maintenance and TEI |
Ericsson |
| R1-2002355 |
Considerations on HARQ/CSI enhancements |
Apple |
| R1-2002461 |
Summary on Rel-16 NR TEI related discussion |
Moderator (NTT DOCOMO, INC.) |
| R1-2002679 |
Discussion on conditions of rate matching pattern overlapping with PDSCH DMRS symbols |
Huawei, HiSilicon |
| R1-2002893 |
Summary on Email discussion [100b-e-NR-TEIs-01] |
Moderator (NTT DOCOMO) |
| R1-2002894 |
Summary on Email discussion [100b-e-NR-TEIs-02] |
Moderator (NTT DOCOMO) |
| R1-2002895 |
Summary on Email discussion [100b-e-NR-TEIs-03] |
Moderator (NTT DOCOMO) |
| R1-2002966 |
LS on subcarrier spacing for CLI-RSSI measurement |
RAN1, LG Electronics |
| R1-2003033 |
Draft CR on half-duplex UE in R16 |
Nokia, Nokia Shanghai Bell |